Non Authoritative Domain Controller (DC) Restore
Environment
Applies to Windows Server 2003 and 2008 based operating systems.
In a ‘Non Authoritative’ restore, one of the following conditions should apply to the destination computer:
Not a domain controller
The only domain controller on the network
One of multiple domain controllers in your network. In this mode, Active Directory data is restored to your computer from a backup, and then updated with the most current version from other domain controllers.
Implementation
To restore a DC in Non-Authoritative mode:
On the Restore Server (Restore Computer):
Install the same operating system and Service Pack levels that were installed on the current Production Server when the System State backup was processed. The OS and SP levels MUST be identical for the System State restore to process successfully.
Assign the same server NETBIOS name and same IP address used by the server before the restore of System State data.
(Note: System State Bare Metal Restores can only be performed on a server with identical hardware as the production server used to process the data backups. Different hardware will cause a bare metal restore to fail.)
Verify the Restore Server’s Disk Management has an identical disk naming structure as the Production Server to minimize restart problems after restoring System State.
Install the same Agent software version on the Restore Server that is currently being used to process data backups on the Production Server (the Agent software versions MUST be identical for the restore to process successfully).
Add the Restore Server Agent as a NEW AGENT in the Agent Console.
‘Reregister as a Previously Registered Computer’ to the Vault using the SAME name as the Production Server via Agent Console > Agent Configuration > Vault Server Tab > NEW Vault Connection (the ‘Reregister’ option will allow the backup catalogs created by the Production Server to automatically be download to the Restore Server – this will not affect your Production Backups. Ensure there are not any scheduled backups running on the Production server during the restore process).
Once the Restore Server Agent has successfully ‘reregistered’ to the vault, and the backup jobs have successfully downloaded to the Restore Server:
Allow several minutes for the restored SYS VOL data to publish after the server has been restarted. Log into the server and review the Event Viewer logs for errors. Once the Active Directory information has replicated from the Primary Domain Controller/Master Schema on the network to the restored server, you will be able to access Active Directory information as needed.
Perform a restore of User Share/Data Files by launching another restore operation for all additional Backup Jobs as needed.
Note: The steps above will NOT publish Active Directory information across your domain from the restored System State data. This restore option is used for Non-Authoritative restores of a single server or multiple domain controllers that will receive Active Directory information from another domain controller on the Network.
Please review and follow the steps above to prepare your restore server for a Bare Metal System State restore operations.