Server 2008 Replication (Restore Backup)

abuhaneef
abuhaneef used Ask the Experts™
on
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..
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Ralph ScharpingDigital Therapist

Commented:
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.
Top Expert 2016

Commented:
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 Architect
Most Valuable Expert 2015
Top Expert 2015
Commented:
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.
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

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?

Author

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 Therapist
Commented:
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.
Top Expert 2016

Commented:
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

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial