Windows Server 2008 R2 Domain Controller Crashed Need To Restore Backup To A New Server

Windows Server 2008 R2 Domain Controller Crashed Need To Restore Backup To A New Server. I did a command line backup and now I'm trying to restore the Domain Controller to a new 08r2 server remotely.

Need help ASAP..

Thanks in advance...
Who is Participating?
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.

Kindly go through this article,

Please confirm the reason you are going through this is the only DC? If you have a separate DC that is functional, do not waste your time trying to restore non AD data.
Seize the roles (ntdsutil) by the remaining DC. Join the new system as another DC.
Then restore the user data and recreate the shares.

Is the backup for system state?
AD data is part of the system state backup.
If your only backup is after this system crashed you might be out of luck.
LHernandez2Author Commented:
Actually we have 3 other DC's for this domain & it wasn't the RID Master but still it's in replication across the entirety.. I've just been asked to restore it & I have a wbadmin backup.
Bootstrap 4: Exploring New Features

Learn how to use and navigate the new features included in Bootstrap 4, the most popular HTML, CSS, and JavaScript framework for developing responsive, mobile-first websites.

The only restore you should be doing is for files.  Not the DC components.
Join the system as an additional DC and let the AD replication work its way through.

Then look through the backup and restore the data files (no c:\windows, program files, etc.0

Shares only. recreate the shares and you should be good to go.

Not sure what or during which period the wbadmin was used to backup, is it an IMage of the prior install?
LHernandez2Author Commented:
Are you saying give the new server the same name and dcpromo it up then restore the C drive?
No. Give it a new name and a new IP and dcpromo it.
Then if there are any shares, I'd suggest using domain based shares (DFS) to avoid server specific dependencies.
LHernandez2Author Commented:
Well right now replication is looking for a domain controller named nrddc1. How will it resolve that if it has a different name?
You need to cleanup the metadata removing all references to the Crashed DC

You of course can reuse the name.
I usually try not to to avoid any errand issues that mayhave existed but not manifested.
LHernandez2Author Commented:
That is a great article. "Where it says If you give the new domain controller the same name as the failed computer, then you need perform only the first procedure to clean up metadata, which removes the NTDS Settings object of the failed domain controller."

Which is the first procedure?
I tend not to reuse the same name unless the rebuild is on the same system.
The first four outlines steps that deal with cleaning up the connection without the need to remove the server entirely.

Windows 2008 is supposed to have an auto-metadata cleanup process, but I am uncertain on whether it occurs after the computer account has been tombstoned.

This article deals with setting the procedures.

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
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
Microsoft Legacy OS

From novice to tech pro — start learning today.