Restoring a corrupt AD...
Discussion
The situation is complicated slightly by the fact that the tape drive in that box stopped working a week ago, so I'l be restoring on a different machine and putting them back manually to try and keep further downtime to a minimum.... (backups for the last week have been to an external HDD sans-system state.)
Can you restore the system state back onto the corrupt DC first to ease the transition? Ok, so it will be a week old but unless you've made lots of changes to AD it would work.
Then backup to disk and copy to new server a'la http://support.microsoft.com/kb/26353
Hard to advise as there are so many variables.
Then backup to disk and copy to new server a'la http://support.microsoft.com/kb/26353
Hard to advise as there are so many variables.
BliarOut said:
Can you restore the system state back onto the corrupt DC first to ease the transition? Ok, so it will be a week old but unless you've made lots of changes to AD it would work.
Then backup to disk and copy to new server a'la http://support.microsoft.com/kb/26353
Hard to advise as there are so many variables.
Then backup to disk and copy to new server a'la http://support.microsoft.com/kb/26353
Hard to advise as there are so many variables.
I don't think there's been any changes to the AD since they had some new machines a month or so ago so I'm golden there. That's a nifty atricle too, I didn't know about the F7 thing!
Cheers!
Neil
Cheers I think so, just cataloguing the tape on another box now.Well, just in case anyone was interested - failed to restore the ntds.dit file.
Got backup exec working in AD restore mode by changing all the service logons (and restore resource credentials) to the DSRM account.
Restored system state from 2 weeks ago - the machine hung for 10 minutes on 99% but finished in the end and rebooted
Would then boot into normal mode - hurray
AD still fecked. Not creating sysvol or netlogon shares. Still trying to replicate to a partner that someone just unplugged and threw away 3 years ago. Couldn't create any new accounts for lack of RID's. Cue much searching of the MS KB. All sorted in the end though!
Thanks for the help. Shouldn't have wasted time messing about trying to repair that file, should have just gone straight into the system state restore! Ah well you live and learn.
Got backup exec working in AD restore mode by changing all the service logons (and restore resource credentials) to the DSRM account.
Restored system state from 2 weeks ago - the machine hung for 10 minutes on 99% but finished in the end and rebooted
Would then boot into normal mode - hurray
AD still fecked. Not creating sysvol or netlogon shares. Still trying to replicate to a partner that someone just unplugged and threw away 3 years ago. Couldn't create any new accounts for lack of RID's. Cue much searching of the MS KB. All sorted in the end though!
Thanks for the help. Shouldn't have wasted time messing about trying to repair that file, should have just gone straight into the system state restore! Ah well you live and learn.
System log still isn't pretty, including the delightful error 'DCOM got the following error: "The operation completed successfully"' Where's bill gates when you need him Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff