NDS Trouble 1

[Jounginator]

Looking for some basic admin info into my troubles:

2 6.5 servers (fileserver with master replica and GroupWise 6.5.1 server with BackupExec 9 for Netware).

Doing my habitual dsrepair | unattended repair on the Groupwise server I ran across this message:

"WARNING: The current dib set name is set to: NDT
ERROR: Unable to set: NDT, as the current dib set, error: -732
NOTICE: You may need to manually rename all NDT*.* & *.NDT files to NDS*.* and *.NDS files.

Repair process aborted."

OK, didn't find any files of that description so maybe restarting the server would clear the condition. Now DS.NLM doesn't load saying it couldn't open local database, error: -723. Mail is still working from hitting the IP address directly (thank goodness!).

What's my next step? The master replica in the fileserver looks good; do I rip out and reinstall ds and resync to that replica? Is that stupid? Or is there something less drastic I can try?

Joung

 

[marvhuffaker]

Ouch. You shouldn't make running an unattended repair a normal routine activity.

Since your DS won't even open, you are most likely in a world of hurt and may need to remove DS and put it back on to recover. But that's not the ideal solution. You'll then have to deal with various other issues that resulted from removing it.

You might also be able to start your server with the -NDB switch, then run dsrepair (Not unattended).. advanced repair, then run the repair that way and see if you can clear up the errors. You should be able to find some tids about the NDB switch and which options to use.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com