Andy's Technotes Home
Tip Jar

NDS/eDir server replacement steps

(emergency, planned, or just to be prepared)

 

Yes I need to update this.

As a general health check of eDir on any given server
ndsrepair -T
ndsrepair -E
ndsrepair -C -Ad -a
This is good to run any time something seems off, there has been network interruptions, and at least once a year on all boxes to make sure nothing has slipped though.

For cleaning out a dead server TID 3338221 and TID 7003130 are still valid in 2022 for starting the process.
Then delete all the dead/crashed server's objects from the tree using iManager (or its eventual successor, or ConsoleOne if you have a really old system).
Now we just need to prod eDir to reconcile all that is gone with the health checks and perhaps a -R rebuild or even -U option. Checking with the previously failing health check step each way




Old stuff that needs work

that still has some good details, and TID numbers if you have old docs


If a server fails (especially within a multi-server tree) see TIDs 3338221 & 10011467 & 10013083 & 10012033. All basically cover the same material but reading them all while waiting for the some of the early steps will help you understand what it is your are doing so that you can do the right things without killing anything. The concepts are the same on all eDir platforms.

Some of the key commands for different platforms.

To remove a failed server from a replica ring on Linux, in Partition, Advanced:

/opt/novell/eDirectory/bin/ndsrepair -P -Ad
Then:
  • Select - A partition
  • Select - View replica ring
  • Select - Failed Server (If if exists)
  • Select - Remove this server From Replica Ring
  • Repeat for each partition.

    If you are changing a server such that you need to take it out of the tree and restore such as when replacing the harddrives or the whole server, then follow TID 10010933 (formerly TID 2934033)

     

    if you are having issues running eDirectory 8.7.3 or later, check TID 3393940, formerly 10093821

    for general NDS things to have checked before calling Novell tech support see TID 2938838 (also was refered to as TID 10014284)

    For proper NDS/eDirectory health check procedures, TID 3564075 (formerly TID 10012858 and 10060600)

    Checkout "10 Tips for TroubleShooting NDS"

    A great reference is Novell's Guide to Troubleshooting eDirectory, by Peter Kuo & Jim Henderson, and my dead-tree edition is 'defaced' by both of their autographs. Wholeheartedly recommended for anyone who has to take care of eDirectory, and still mostly valid in 2022.

     

    Additional NDS health information is available on the following App Notes (available on the Support Connection CDs or at http://developer.novell.com/research/index.htm as viewed through the WayBack Machine)
    May 1998 Using DSREPAIR to Maintain the Novell Directory Services Database
    August/October 1997 Maintaining a Healthy NDS Tree: Parts 1 & 2

    details for maintaining NDS
    January 1999 Troubleshooting NDS in NetWare 5 with DSREPAIR and DSTRACE

    and an old but still useful for understanding the basics even if some of the details have changed
    October 1996 Backing Up and Restoring Novell Directory Services in NetWare 4.11


      All Novell TIDs (Technical Information Documents) can get gotten on Novell's Support Connection CDs and at their online Knowledge Base. Old TID numbers included for use on those old portable Knowledge databases.
    An early instance of this I shared with a friend at Novell got posted as my Cool Solution.
     

    Last updated 2022-01-25 Copyright © 1996-2022 Andy Konecny andyweb @ konecnyconsulting.ca