Server 2008 Replication (Restore Backup)

We recently had one of our servers crash. The server (Server1) was running 2008 R2. It was a domain server and the only backup that we had was from 3 months ago. Since the time of the last backup we added another server (Server2) and enabled replication from the first.  The question is that if we restore the backup from 3 months ago, will it overwrite Server2 with old data?  What is the best procedure to restore the old backup and get the updated Active Directory information on it from Server2..
abuhaneefAsked:
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.

Ralph ScharpingDigital TherapistCommented:
When you say replication do you mean file replication (FRS) or replication of objects within AD?
Since there are no first and secondary servers in AD, newer data should never be overwritten by old.
You could if you want to be safe, restore your backup offline, and remove AD.  Seize the FSMO roles on your Server2, remove Server1 as repliation partner, then set Server1 online again and dcpromo-te it back.
David Johnson, CD, MVPRetiredCommented:
install from scratch and replicate it back.. you are within the tombstone time of 180 days but this is probably the safest route.
Will SzymkowskiSenior Solution ArchitectCommented:
There are 2 types of backups when it comes to AD.

Authoritative and Non-Authoritative.

Authoritative is used you want to recover something that has been mistakenly configured or deleted and you want to revert this change back to that it was previously.

Non-Authoritative is when you are simply restoring a DC from a state in time and when it comes online it will broadcast to the other DC's to send up to date replication data (chagnes) that is does not have.

Non-Authoritative is the default choice. Authorirative is hardly used anymore as there are new means of restoring deleted objects etc i.e. recycle bin. It is still however an option if needed.

If your FSMO role holder failed and this is the one that you are trying to restore then i would recommend Seizing the roles to server 2, perform a Metadata Cleanup to remove Server1 from AD and then install a new OS on server1 add it to the domain and re-promote.

Using your system State backup is not a valid method in this scenario.

Will.
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

abuhaneefAuthor Commented:
I do believe Server1 was the FSMO  role holder.  Server2 is currently serving as AD, DNS, and DHCP.    Is there a process for seizing all FSMO roles?
abuhaneefAuthor Commented:
The backup that we have is a full image backup.  I was able to restore it to other hardware, but will only boot to DSRM (Safe Mode).
Ralph ScharpingDigital TherapistCommented:

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
Ralph ScharpingDigital TherapistCommented:
Clean up your remaining network, first.  Then get the restored machine back so that it is not in a domain.
Domain-Join it, then promote it to domain controller.
afterwards you can transfer the FSMO roles back to whatever machine you want to have them.
David Johnson, CD, MVPRetiredCommented:
Move-ADDirectoryServerOperationMasterRole -Identity “BRAVO” -Force -Verbose –OperationMasterRole PDCEmulator,RIDMaster,InfrastructureMaster,SchemaMaster,DomainNamingMaster 

Open in new window

Simple powershell script runas administrator on the surviving DC and change -Identity "BRAVO" to the DC Name or use
$env:Computername
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.