- Turn off inbound replication. (http://technet.microsoft.com/en-us/library/cc787395.aspx)
- If you do not have a current backup of the recovery domain controller, Back up system state. You can use this backup if your recovery is not successful and you can try again. (http://technet.microsoft.com/en-us/library/cc787254.aspx)
- Restart the domain controller in Directory Services Restore Mode Remotely as the DC is not physically near me. (http://technet.microsoft.com/en-us/library/cc779687.aspx)
- Mark the object or objects authoritative. (http://technet.microsoft.com/en-us/library/cc757068.aspx)
- Restart the domain controller normally.
- Synchronize replication with all partners. (http://technet.microsoft.com/en-us/library/cc778969.aspx)
- Run an LDIF file to recover back-links in this domain. (http://technet.microsoft.com/en-us/library/cc786564.aspx)
- Turn on inbound replication. (http://technet.microsoft.com/en-us/library/cc783692.aspx)
- Back up system state on the recovered domain controller.(http://technet.microsoft.com/en-us/library/cc787254.aspx)
- If the .ldf file shows back-links for objects in other domains, perform the procedures in Procedures for recovering group memberships (and any other back-link attributes) in other domains. (http://technet.microsoft.com/en-us/library/cc779573.aspx)
One thing to take note if you are restoring GROUP. You must make sure all the users are already restored!! If not, you will encounter a lot of un-neccessary additional follow up~
I really hope that such scenario will not happened and one way to prevent is to make sure Domain Admin Rights or Rights to manage OU\Users Account\Computer Account are granted only to limited user in your IT Team.
And most important is one should always be careful with all the changes to the Objects in the AD especially comes to moving or deletion!!