[Intel Navigation Header]

    StorageExpress(TM) System: Recovering a 4.x File Server

    Contents:

    • STORAGEEXPRESS(TM) SYSTEM: RECOVERING A 4.X FILE SERVER
    • 4.X SERVER DOESN'T APPEAR ON THE LAN WHEN NDS IS CORRUPTED
    
    

    STORAGEEXPRESS(TM) SYSTEM: RECOVERING A 4.X FILE SERVER

    
       The following are assumptions for a complete restoration of the total
    
       file structure and NetWare Directory Services (NDS): 
    
    
    
         1. A valid Storage Management System (SMS) aware backup of the file
    
            server file system and NDS exists.
    
    
    
         2. The server was part of the tree being restored.
    
    
    
         3. The users were installed in the directory tree using NWADMIN or
    
            NETADMIN.
    
    
    
       Procedure
    
    
    
       A:  Preliminaries 
    
    
    
         1. In a multiple server tree, do the following: 
    
    
    
           a.  Login to the tree and remove the volume from its location within
    
              the tree using NWADMIN or NETADMIN.
    
    
    
           b.  Use PARTMGR to remove the file server name from the tree.
    
    
    
           c.  A MASTER replica must exist for each partition in the tree.  If
    
              there is not one, then you will have to make one of  the current
    
              *read / write* or *read only* partitions the MASTER before
    
              reinserting the file server into the current tree. To assign a
    
              MASTER replica, use PARTMGR or run DSREPAIR on another active
    
              server in the tree.  In DSREPAIR select option 4 to *Repair
    
              replica ring with no master* and assign another replica as 
    
              MASTER when prompted.
    
    
    
       B:  Installation of the Server 
    
    
    
         1. Install the file server from scratch and install NDS using the same
    
            tree and organization as the original.
    
    
    
           a.  If the file server was in an existing tree, then put the server
    
              back in the same location on the existing tree.
    
    
    
           b.  If the server was a single server in a tree, then give this tree
    
              the exact name as the original tree name.
    
    
    
       C:  Restoration of the NDS 
    
    
    
         1. Restore the NDS using the SMS compliant backup.
    
    
    
           a.  If any files from the backed-up server still reside on any of
    
              the current volumes, trustee assignments from the backed up files
    
              server will be invalid.   DSREPAIR then needs to be run to remove
    
              all trustee  assignments.  This is done by selecting option #6
    
              *Check file system for valid trustee ID*s*.
    
    
    
              With the restoration of the directory tree into the newly created
    
    
    
              Directory, each object is assigned a new ID which most likely
    
              will not match the original.  (When the TSA does the backup of
    
              the trustee nodes, the ID number is used to get the full object
    
              name and replaces the ID number which is then written to tape.)
    
    
    
              Upon restoration, the trustee node is read from the tape, then
    
              the new ID is retrieved from the current NDS.  Then that ID
    
              number is written to the trustee node and in turn written to the
    
              hard disk*s Directory Entry Table (DET).
    
    
    
         2. When to Restore NDS: 
    
    
    
           a.  If this server is being replaced in a multiple server tree, the
    
              tree is still intact and a master partition is installed on
    
              another server.  NDS does not need to be restored.
    
    
    
           b.  If this is a single server tree, then restore the NDS on  the
    
              server.  Check to make sure there are no unknown objects in the
    
              place of previously known object  types.  If there are, then the
    
              NDS may need to be  restored multiple time until all the unknown
    
              objects are defined.
    
    
    
       D:  Restoration of the file system.
    
    
    
         1. Restore the file system using the SMS compliant backup.
    
    
    
           a.  All the trustee nodes need to be restored on all volumes.  The
    
              files should be restored where needed.
    
    
    
           b.  If the files are already on the volume the *Trustee Rights Only*
    
              can be restored by restoring the  directories.
    
    
    
         2. At this point, you are back in business.
    
    
    
       Notes:
    
    
    
         *  SMS backups of the NetWare 4.x server file system back up the
    
            trustee nodes by name, not by ID number.  When the restore is in
    
            process the objects are assigned a new ID from the recently
    
            installed NDS.
    
    
    
         *  The file system subdirectories matching previous object ID*s will
    
            be different after the NDS is restored from tape.  Therefore,
    
            bindery objects such as mail directories with the login scripts
    
            will not have the same  assignment after restoration.  The queues
    
            will need to be recreated.
    
    
    
         *  Trustees must ALWAYS be the last group of data restored to get the
    
            proper trustee ID assignments even if NDS was restored from a
    
            replica in the current tree.
    
    
    
         *  Partition and replica information is not backed up.
    
    
    
         *  During a backup the NDS is the first session, it is a separate
    
            session which includes the ENTIRE tree.  In the Browse Tape Catalog
    
            screen the session is displayed as:  
    
    
    
            Example:  *FS1A/Full Directory  Backup:*
    
    
    
       Some common questions about restoring NetWare 4.x Servers
    
    
    
       Question:  If I backup just a single file, will the NDS also get backed
    
       up?
    
    
    
       Answer:
    
       No.
    
    
    
       Question:  If I backup the directories System & Public only, will the
    
                 NDS be backed up?
    
    
    
       Answer:
    
       No.
    
    
    
       Question:  Can the StorageExpress system restore just the NDS?
    
    
    
       Answer:
    
       Yes.
    
    
    
       Question:  Does the StorageExpress system have an option to backup just
    
                 the NDS?
    
    
    
       Answer:
    
       No, the only way to backup just the NDS is to select a full backup of a
    
       volume and let the first session  finish. When the second session
    
       starts, cancel the backup.
    
    
    
       Question:  Can the StorageExpress system backup only a container or
    
                 object of the NDS?
    
    
    
       Answer:
    
       No, only backs up the entire NDS.
    
    
    
       Question:  How would I verify that the NDS was backed up?
    
    
    
       Answer:
    
       Check the Activity.log , it will display information similar to the
    
       following: 
    
    
    
            Connected with TSA FS1.Netware 4.0 dir 
    
            Process all files via SMDR 
    
            Backup FS1/Full Directory Backup to tape_name_FS1 sequence 1
    
            session 1 
    
            14 files 48kb written to tape_name_FS1 @ 1,440 KB/MIN 
    
            Netware Directory Services Database Backed up 
    
            Connected with TSA FS1.Netware file system 
    
            Process all files via SMDR 
    
            DOS files will be processed via TSA 
    
    
    
       The "Browse Tape Catalog" screen will show: 
    
    
    session # source directory status 1 FS1/FULL DIRECTORY BACKUP COMPLETED [this is the NDS backup] 2 FS1/SYS: ABORTED
    The *File Tracker Browser* screen & the *Select Volumes, Directories, & Files for Restore* screen will show:
    [] FULL DIRECTORY BACKUP: [no files will be located here, but this is the NDS backup] [] SYS: [this will show the directories & files that have been backed]
    Question: How would I verify that the NDS was restored? Answer: Check the Activity.log, it will display information similar to the following: Restore job_name sequence 1 session 1 to FS1/Full Directory Backup 14 Files 25 KB restored to FS1/ Full Directory Backup @ 1,440 KB/MIN 1 session(s) 14 files(s) 48KB processed Restore operation successful Question: I deleted a user but none of the files/directories were deleted. I then restored the NDS to get the user back. Why didn*t the user rights return? Answer: The trustee rights are kept in the directories. When the user was deleted the rights were removed from the directory. To get the users rights back, restore the directories. To make sure some data does not get over- written you can chose one of the restore options under *On Conflict* like SKIP. When restoring the NDS use ONLY THE DEFAULT settings in restore. Question: How do I do a MANUAL RESTORE of the NDS? Answer: 1. Select Manual Restore from the *Restore Menu*. 2. Set the following options in the *Manual Restore Options and Schedule* screen. a. Tape name = * b. Session number = 1 c. Select *Write Restored Files to* button and select the name of the server & the SYS: volume. Supply the login ID & password when prompted. d. Select "Source Path" button, In the "Session Restore Source Path" screen. Type in "*.*" and select *Add Item* button. Select "Source List" button choose "Files". In the Source Path screen, setup fields in the following manner: Fully Qualified Path: [Example: \system\*.*] *.* List: *.* Source List: (X) Files e. Leave the *Restore Options* screen to the default settings. 3. Done.

    4.X SERVER DOESN'T APPEAR ON THE LAN WHEN NDS IS CORRUPTED

    
       Symptom:
    
       If the NDS is corrupted, the 4.x server may not appear on the LAN when
    
       using the NLIST or SLIST  commands...However DISPLAY SERVERS will show
    
       the file server as being present.
    
    
    
       The corrupted bindery may let a user login but not the Storage Express.
    
    
    
       NLIST may return an error message *An error prevented Bindery from being
    
       read*.
    
    
    
       Solution:
    
       To fix a corrupted Bindery:  first run DSREPAIR on the target server. 
    
       It may be necessary to remove the NDS & recreate it using NetWare *Load
    
       Install* program.
    
    

    Trademark information