Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

dead domain controller

Status
Not open for further replies.

dpowell1

MIS
Mar 30, 2004
57
US
Our company has three DCs (2 in our main office and 1 in via WAN). The hard drive in one of the DCs (main office) died yesterday. We have a copy of that DC from a week ago. If we simply replace the drive will it sync up OK with the two working DCs or can it cause problems with our AD?
 
If all servers are a DC and you have an exact image of the server that died then yes. If your recreating this server from scratch then you will have to remove the old one manually, also do not give it the same name as that will cause issues.
 
Yes, it's a drive we pulled out of the RAID array of the dead DC last week so we can just put it in and the bax will come back to life. I just wanted to make sure that there were no negative ramnifications from the AD side to bringing back a DC with one week old AD info.
 
Ummmm I would not use an old backup in that way, you'll end up with USN rollbacks....

If the dead DC held and FSMO roles then seize them to another box

Clean up the AD metadata

Wipe the machine, re-install windows, promote to DC (I always use a different name in this scenario for the dc that has failed and been rebuilt)

Paul
VCP4

RFC 2795 - The Infinite Monkey Protocol Suite (IMPS)

Difficult takes a day, impossible takes a week
 
Bummer, no easier way to get this DC to pickup the newer AD info off the good DCs?
 
If a single drive failure brought down your DC, it's time to reasses your hardware configuration. You should be able to survive a single drive failure with no interruption of services.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
Actually it wasn't a drive failure but rather bad memory. Both of the RAID1 drives were rendered unbootable.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top