Worst Scenario Distaster AD Recovery

  • Thread starter Thread starter Alexander V. Alexeev
  • Start date Start date
A

Alexander V. Alexeev

Good day,

A small network run on Win 2000 AD has lost its only DC and coincedentally a
backup server which was hosting network share where the sys backup was being
thrown routinely. Power outage over weekend + ups failure. So two servers
are down - the backup one is unreadable filesystem showing nothing, i.e.
80Gb of 80GB are free!
Whereas the DC does not boot, blue screen appears at various stages of
booting Win 2000 Server Logo saying :
IRQ_NOT_LESS_OR_EQUAL and some other messages. I have checked it's not the
memory or the motherboard that is faulty and also plugged in a spare WinXP
loaded HDD which actually shows the DC's system disk intact (at least file,
folder structure). Still, however, I suspect it does not boot coz of its HDD
had bad blocks or smth corrected by automatic chkdsk...

I am investigating http://support.microsoft.com/kb/263532 to see if it has
any relevance to this situation but have my doubts it will only take time
and not help much since the harddrive seems to be the culprit. I have
managed to copy with no probs the Winnt\NTDS and SYSVOL folders out this
hdd. Has anyone perhaps managed in their experience to raise a "blank" DC
and feed it somehow the old PDC's datafiles to restore AD this way?

Or if I have to eventually raise a whole new domain, any way I could map the
exisiting profiles on client machines to their new accounts without having
to generate new profiles and settings? Shall the new domain be the same name
as old one or it won't help to be so?

Thank you!
Regards
Alex A
 
Thank you for encouragement. I was doing it the d4 way and managed to
restore AD to a serviceable state. Then discovered after late night playing
with the hardware that the reason the DC failed to boot was a fault with one
of the two CPUs... sometimes I wish the hardware component died flat rather
than functioning and generating weird hard to troubleshoot glitches :).

Anyway, the d4 thing was crucial in restoring SYSVOL and NETLOGON shares.

Regards
Alex A
 
Back
Top