Instructions in the following sections explain how to restore eDirectory for a specific server when you have a hardware failure. For information on backing up and restoring eDirectory on NetWare on an entire tree, refer to Using Backup and Restore Services on NetWare.
In a multiple-server environment, one server can 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. A hard disk failure involving volume SYS: affects the entire server and halts all NetWare operating system activities. Because the eDirectory files are stored on volume SYS:, losing this volume is equivalent to removing NetWare and eDirectory from the file server.
To restore eDirectory to a single server, you will need to complete the following procedures:
Step-by-step instructions are contained in the following sections.
The following procedure assumes you have a current backup of the server-specific information for the failed server.
IMPORTANT: If you do not have a backup for the failed server, you will need to remove the server object from the tree and restore eDirectory as explained in Novell Technical Information Document #10011467.
From your backup host server, run SMSTM and restore server-specific information files from a tape backup.
The server-specific information files are restored to a subdirectory in SYS:\SYSTEM on the server you have selected. The subdirectory name is a DOS 8.3 name derived from the source server name.
The following files are restored:
SERVDATA.NDS contains server-specific NDS information that allows trustee assignments and other NetWare information to be preserved.
DSMISC.LOG contains a list of replicas, their types, and other servers that participated in the failed server's replica ring.
VOLSINFO.TXT contains information about the server's volumes, including name space, compression, and data migration information.
STARTUP.NCF is the NetWare server boot file that loads the server's disk driver and name spaces and some SET parameters.
AUTOEXEC.NCF is the NetWare server batch file that loads modules and sets the OS configuration.
Make these files easily accessible for use during the remaining process.
For complete information on using SMS, see the Storage Management Services Administration Guide.
This procedure explains how to
Reassign master replicas: If the failed server holds a master replica of any partition, you will use DSREPAIR to designate a new master replica on a different server in the replica list.
Remove replica list references to the failed server: Each server participating in replica rings that included the failed server must be told that the failed server is no longer available.
Use the information contained in the DSMISC.LOG file to determine which replicas were stored on the failed server.
At the console of one of the servers that shared a replica with the failed server, load DSREPAIR -a.
WARNING: If used incorrectly, using DSREPAIR with the -a option can cause damage to your tree. For more information on these options, refer to Novell Technical Information Document #2938493.
Select Advanced Options Menu > Replica and Partition Operations.
Use this option in DSREPAIR only when the master replica of a partition is lost because of a server or hardware failure.
Select the partition you want to edit.
Select View Replica Ring to see a list of servers that have replicas of the partition.
Select the server you want to hold the master replica > select Designate This Server as the New Master Replica.
The replica ring now has a new Master Replica. All replicas participating in the ring will be told that there is a new master.
Step back one menu to where you can select View Replica Ring > choose the name of the failed server.
Select Remove This Server from the Replica Ring > log in as Admin.
After reading the explanation message, enter your agreement to continue.
Exit DSREPAIR.
All servers participating in that replica ring will be notified.
Repeat this procedure as applicable on one server for each replica ring that the failed server participated in.
This installation procedure accomplishes the following:
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 VOLSINFO.TXT file to verify configuration information.
Install NetWare.
See the NetWare Installation manual for details about starting install.
During installation, re-enter the same server name, eDirectory context, and network address that the server had prior to the failure.
Use the STARTUP.NCF and AUTOEXEC.NCF files 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.
Using a new tree name prevents server identity conflicts.
Copy the restored server-specific files from the backup host server to the newly installed server.
These files need to be available for reference for the following steps.
At the server console prompt, type NWCONFIG.
Select Directory Services Options > select Remove Directory Services from This Server > log in to the tree.
Removing the directory allows you to restore the failed server's identity completely and restore it to the original tree.
Select Directory Services Options > Directory Backup and Restore Options > Restore Local Server Information after a Hardware Failure.
Press F3 to specify the path to SERVDATA.NDS.
eDirectory is restored at this time, using the information contained in SERVDATA.NDS. Once this is done, eDirectory is fully functional on the server, except that the partitions and replicas have not yet been re-established. Reestablishing replica rings is done after install.
Prepare the restored directory for integration into the original tree by executing the following DSREPAIR commands in the order specified:
WARNING: The following DSREPAIR switch commands should only be used in this procedure and should be executed in the order given. DO NOT use these commands for general DSREPAIR operations.
This is a clean up process. It's ok to see error messages displayed during the clean up.
Use DSTRACE to verify that the schema has synchronized fully. From the NetWare console, type
Press Ctrl+Esc > select Directory Services to view the trace screen. Watch for the message "All processed = YES."
Once the schema is synchronized, you are ready to do a file system restore.
From the server console enter TSA500.nlm to load the file system TSA.
Use SMS to start the restoration of the file system for each volume affected by the failure.
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.
After the restoration of the file system is completed, down the server and bring it back up.
This process ensures replication on the new server will be at the same level as it was on the failed server.
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 edit dsmisc.log to view the log file contents.
Re-establish replicas on the failed server using ConsoleOne.
In the left pane, right-click the root container of the partition that you want to replicate > click Views > click Partition and Replica View.
On the toolbar, click Add Replica.
Next to the Server Name field, click the browse button > select the server you just restored > click OK.
Select the type of replica you want > click OK.
If the failed server had master replicas, you can designate that same set of replicas as master replicas.
For information on using ConsoleOne, see the online help.
Use ConsoleOne to verify a successful restoration.
Right click the server in the left pane > click Views >Partition and Replica View.
You can use the NDS User Security Reports to get a complete listing of trustees and their assigned rights. See Generating Reports in ConsoleOne User Guide.