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.
J. Jason LaCroixAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

pjamCommented:
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.
:)
1
CompProbSolvCommented:
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.
1
sAMAccountNameSr. Systems EngineerCommented:
The default Tombstone Lifetime value for AD 2008 and newer is 60 days.  If you chose to recover the DC, you should be able to do so safely however there may be unexpected changes that will replicate outbound from that DC...  This may cause more confusion than its worth at this point.  Personally, I'd simply scrub it from the domain/forest and rebuild it.
1
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

Ben Personick (Previously QCubed)Lead Network EngineerCommented:
Default tombstone lifetime is 60 days.

If you're running anything newer than windows 2000, you can even rescue domain controllers which have exceeded thw tombstone lifetime.  Just longer more annoying process.

However at 27 days nothing to worry about, you'll probably have some basic replication problems, but usually a couple reboots and some forced syncs will shake that out.

Run RepAdmin /ReplSummary on each DC a couple times after the old DC comes back up see iff its complaigning about passwords being expired ans no PDC, if so give another reboot force AD sync when it comes back up wait 15 minutes more and diagnose any remaining replication problems.

At that point it may still shake itself out given a little longer, depends on your replication topology and number of sites/DC.

if not then diagnose the problems from RepAdmin/replesum and the event logs to resolve any remainaing replication issuses
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
J. Jason LaCroixAuthor Commented:
thanks to all who contributed answers to my post. it is much appreciated. well done.
0
Ben Personick (Previously QCubed)Lead Network EngineerCommented:
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.
0
Ben Personick (Previously QCubed)Lead Network EngineerCommented:
glad to help
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.