This topic contains the following:
NOTE: Remote repair operations can only be performed on NetWare* servers. Remote repair operations for servers other than NetWare can be performed by running DSREPAIR at the server's console.
In an NDS tree, the ID for an object is unique on each server. The remote server ID list contains a list of IDs for this server's object as it is found on other servers' databases. If the remote ID is incorrect, this server may return an NDS error, indicating that it cannot authenticate to the remote server.
This operation will verify the remote server's name, the remote server's ID in this server's database, and the remote ID, which is this server's ID as it is found in the remote server's database. If any errors are detected, this operation will attempt to repair the server IDs.
This operation does not lock the NDS database, so you can run this operation as an initial troubleshooting option if you identify NDS errors in Partition Continuity.
Repairing a replica consists of checking the replica ring information on each server that contains a replica, and validating the remote ID information. This operation repairs only the chosen replica.
If you have not performed the Repair Local Database operation within the last 30 minutes, you should do so before performing this operation.
You can repair network addresses to ensure that the servers in your network are broadcasting correct addresses.
This operation checks the network address for every server in the local database by searching for the server's name in the local SAP tables.
If this operation finds an address in SAP, it compares this address to the NetWare Server object's IPX network address property and the address in each replica property of every partition root object.
If the address it finds differs from these, this operation updates it. If this operation cannot find a SAP name-to-address mapping, then it cannot make a repair for that server.
If you are getting DS errors related to communication between servers, you can repair network addresses as a troubleshooting option since it will not lock the NDS database.
You can repair your local database records when you find that your NDS database is corrupted. This operation resolves inconsistencies in the local Directory database so that it can be opened and accessed.
After the repair is completed, a log of the repair operations is displayed. Inspect the repair operations in the log to see if additional work is needed to complete the repair.
If objects in a replica are damaged, delete the replica and add it back, or receive updates from the master replica to make sure it is synchronized with the other replicas in the partition.
If you select this option, there will be a short period of time when users will have limited access to resources on the server where you are running this operation.
Don't use this feature to change a replica type. This is a repair feature that should only be used when the current master replica is corrupted or lost.
Assign a new master replica if the current master replica is corrupted or if the server the current master resides on loses data integrity or experiences hardware failure.
You need a master replica to perform operations with a partition. Assigning a new master replica allows you to convert an existing replica to the master replica, and allows you to perform partitioning operations.
Misuse of this operation can cause irrevocable damage to the NDS tree.
If a server that is no longer in the tree appears in the replica ring, instead of using the Remove Server operation, perform a Delete Server operation to delete the server's object.
Over a period of time, the server object will be deleted and the replica ring will be updated accordingly. (This period of time ranges from minutes to several hours.)
If the NDS tree is sufficiently damaged to prevent a Delete Server operation from completing normally, or if a server exists in the replica list which no longer has a replica of the partition, you may then have to use this operation.
Remove a server from a replica list when other servers are trying to synchronize with a server that has no replicas of the partition.
For example, in the Partition Continuity view---or upon running DSTRACE on the server---you might find errors indicating that a server still has record of another server in its replica list when the second server no longer contains a replica of the partition in question. Use the Remove Server operation to remove the second server from the first servers replica list.
NOTE: NDS Manager will attempt a safer Delete Replica operation each time a Remove Server request is made. If the Delete Replica cannot be done, NDS Manager will prompt the user to continue and go forward with the Remove Server operation. If NDS Manager is able to do a Delete Replica operation, the dialog will reflect this in the titlebar and no log file will be displayed afterward. If the Remove Server operation is done, NDS Manager will display the log file upon completion of the operation.
This operation checks the association of all the mounted volumes with Volume objects in the Directory.
If the volume is not associated with a Volume object, this operation looks for one in the context of the NetWare Server object. If the volume is found, then the Volume object is attached to the volume.
If the volume is not found, then this operation attempts to create one.