In a multiple-server environment, it is possible for one server to go down while the rest of the servers in its replica list remain intact. If the hard disk containing volume sys: on one server becomes damaged, the entire server is affected since a hard disk failure involving volume sys: affects the entire server and halts all NetWare operating system activities. Because the NDS files are stored on volume sys:, losing this volume is equivalent to removing NetWare 5 and NDS from the file server. If volume sys: fails, you must reinstall NetWare 5 and NDS before you restore your data. The following procedure assumes you have a current backup of the server-specific information for the failed server.
From your backup host server, run SMS and restore Server-Specific Information from a tape backup.
For information on using SMS, see Backup and Restore.
The server-specific information files (servdata.nds, dsmisc.log, volsinfo.txt, startup.ncf, and autoexec.ncf) will be restored to a subdirectory under sys:system on the server you have selected. The subdirectory name will be a DOS 8.3 name derived from the source server name. These files will be used throughout the restore procedure.
If the failed server held a master replica of any partition, use DSREPAIR to designate a new master replica on a different server in the replica list. (Use the information contained in the dsmisc.log file to determine which replicas were stored on the failed server.) For information on using DSREPAIR, see the online help.
If no other server contains the same replicas as the failed server, repeat step 2 on another server that contains the missing replicas. Use the replica list in dsmisc.log to determine which servers to load DSREPAIR on to complete this step.
To change the replica type, run DSREPAIR on another server in the replica list that has an active Read/Write replica of the partition, as follows:
Load DSREPAIR -a
WARNING: If used incorrectly, DSREPAIR -a options can cause damage to your tree. For more information on these options, refer to Technical Information Document TID #2938493.
Choose Advanced Options Menu.
Choose Replica and Partition Operations.
NOTE: Normally, you should use NDS ManagerTM to perform partition operations. This option in DSREPAIR is to be used only when the master replica of a partition is lost because of a server or hardware failure.
Choose the partition you want to edit.
Choose View Replica Ring to see a list of servers that have replicas on the partition.
Choose the server you want to hold the master replica and select Designate This Server as the New Master Replica.
If the failed server contained any non-master replicas, you need to remove all replica pointers to the failed server. If no other server contains the same replicas as the failed server, repeat step 3 on another server that contains the missing replicas.
Use dsmisc.log to determine which other replica types the failed server contained and to determine which servers to load DSREPAIR on to complete this step.
Remove the failed server from the replica ring, as follows:
Install the new hard disk or server hardware.
Follow any instructions provided by the manufacturer to verify that the server's hard disks are working. The new hard disk should have the same (or larger) storage capacity as the drive it replaces. Use the server-specific information files to verify configuration information.
At the system console prompt, enter the following to install NetWare 5 on the new server:
INSTALL
When prompted re-enter the same server name, NDS context, and internal IPXTM number that the server had prior to the failure.
Use the startup.ncf and autoexec.ncf files included with the server-specific information for needed information.
When prompted to enter a tree name, enter a new tree name so the server will install into its own temporary tree.
The installation is now complete.
Load NWCONFIG. From the Directory Services Options menu choose Remove Directory Services and log in to the tree.
From the Directory Services Options menu, choose Directory Backup and Restore Options > Restore Local Server Information After a Hardware Failure. Specify the path to servdata.nds or to the Server-Specific Information.
Press F3 to specify the path to where the server-specific information files were stored in step 1. Press Enter to copy the files to the new server.
Dsmisc.log and volsinfo.txt are copied to a subdirectory of the sys:system directory along with autoexec.ncf. Startup.ncf is copied to the c:\nwserver directory.
NDS is also restored at this time, using the information contained in servdata.nds. Once this is done, NDS is fully functional on the server, except that the partitions and replicas have not yet been re-established.
Now you are ready to do a file system restore.
At the console, load the file system TSA and enter
LOAD TSA500.NLM
Use SMS to start the restore of the file system for each volume affected by the failure.
NOTE: If the server that failed was the host server for the backup program, first take the steps necessary to reinstall the backup software and storage device drivers.
If the server had volumes other than sys: that were unaffected by the failure, no further action is needed because the servdata.nds file preserves the trustee assignments on these other volumes.
After the restore of the file system is completed, down the server and bring it back up.
Re-establish replicas on the failed server using NDS Manager. For information on using NDS Manager, see the online help.
Use dsmisc.log to aid in this process. It contains a copy of the replica list that resided on the server at the time the backup was made.
From the server console, enter the following to view the log file contents:
load edit dsmisc.log