That almost sounds like data corruption caused by faulty SAN
Any idea what caused either problem ?
I always try to read up on disasters other people are having so if it
happens to me I might recognize it sooner and hopefully have a few
things to try and fix it, so far that’s worked pretty well
Although I’ve been very lucky disaster wise (knock on wood!)… I
almost lost our entire DS once because DirXML wanted to delete
everything when I wanted to start over and deleted all the AD objects …
lucky me it first deleted the account it was logged in with itself…
When I started working the eDir was in shambles pretty much … tons of
sync problems and server lockups because of 1 specific server … and
then the NCE (or A … I forgot) left … I did some terrible things to
our DS from TID’s that had big letters saying ‘DO NOT DO THIS WITHOUT
NTS TELLING YOU TO’ like destroying replicas and I have no idea what
else … But eventually I managed to straighten everything out and we got
rid of the bad server. When adding an identically named server back into
the tree like a year later there was an immediate excess of red text in
ndstrace … since then we blacklisted the name
All my other problems were either caused by broken service packs,
BackupExec(when Symantec took it over) or hardware failures.
Yes had also such a disaster with a DSfW server some time ago. In my
opinion Novell has forgotten to think on proper disaster recovery
procedures in all of its lastest products - maybe except groupwise.
This issue can occur and it could be cured easily, if Novell would -
the case of a corrupt dib - just allow the ndsd to startup without dib
and automatically recreate the dib from the still intact replicas on
the other servers. But that option is not even available. In former
times of old Netware (like 4.x) you could just remove edir and
afterwards readd it, but that’s getting you directly into full
on an OES Linux box.
jamesgosling sounds like they ‘said’:
eDirectory runs like a dream on SLES! DSREPAIRS on warp drive![/color]
So my response to jamesgosling’s comment is…
Usually, but I had a major issue that started last friday evening.
One oes11 server had ndsd core, apparently there were db block issues
in nds.db that caused the core. after which ndsd would not start.
Had a second server do the same thing over the weekend. Spent 20ish
hours on the phone w/ NTS to get things running properly again, had
major tree & schema damage from this…[/color][/color]
Conz’s Profile: http://forums.novell.com/member.php?userid=54211
View this thread: http://forums.novell.com/showthread.php?t=458973