Link to home
Create AccountLog in
Avatar of J. Jason LaCroix
J. Jason LaCroixFlag for United States of America

asked on

When is it too late to power back on a Secondary DC that's been offline for 26 days?

We had a backup server's hardware fail & take out one of our secondary domain controllers with it. The failed dc is a writable Windows Server 2008 R2 but with no FSMO roles attached to it. The hardware has been fixed but the secondary dc has been offline for 26 days now. Is it safe to bring back online without any consequences?

Both our Primary (Windows Server 2012 R2) and two other secondary's (Windows Server 2012 R2 & Windows Server 2008 R2) have remained online during this time frame and our functioning correctly.

Thanks for your time.
Avatar of pjam
pjam
Flag of United States of America image

I believe it tombstones or whatever it's called in 30 days.  So make haste if this is true or a lot of work will be needed.
:)
Avatar of CompProbSolv
I think that the default setting is 60 days, but it can be changed.

You should be able to bring the repaired server online and have it replicate properly.  On the other hand, if you have 3 DCs that are working properly I would consider removing and reinstalling AD on the server and then promote it.  It should get everything it needs from the other DCs.
SOLUTION
Avatar of Ed OConnor
Ed OConnor
Flag of Ireland image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
ASKER CERTIFIED SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Avatar of J. Jason LaCroix

ASKER

thanks to all who contributed answers to my post. it is much appreciated. well done.
note I assume this was just a hardware failure, and you didn't restore a backup of the DC.

 If you did restore a backup of the DC, then DO NOT turn it on, that can cause major issues with your domain.

restoring DCs from backup requires a very specific set of steps, I find in that case its always easier to treat the DC as lost, clear the meta Data for it, build a new replacement DC from scratch and join it and then promote it verses dealing with getting the restore right.