Domain controller recovery is the process of restoring a domain controller from scratch in the event of a complete breakdown. Without a potent disaster recovery plan, unforeseen events such as hardware failure or ransomware attacks can impede routine IT work and business processes.
In this guide, we'll explain how you can configure a domain controller for backup and the steps you can take to perform its restoration.
Domain controllers have two modes of restoration:
A domain controller can only be authoritatively restored after non-authoritative restoration is complete.
Prerequisites:
You will need at least one valid domain controller backup to perform a successful domain controller restoration. Refer to this guide to learn how you can configure a domain controller for backup using RecoveryManager Plus.
Creating a domain controller backup and performing restoration is a two-step process:
After configuring the backup setting, the backup agent will be installed in the selected servers and domain controllers. A backup of the selected domain controller will be made at the time specified in the configuration.
Once you’ve created a domain controller backup, you can use that to perform a domain controller restoration.
A recovery media is a minimal OS with limited functionalities that contains all data required to boot your machine and run RecoveryManager Plus' restoration wizard. Once created, it can be used to restore multiple domain controllers. Irrespective of the physical machine's version, you will only need one recovery media for all the domain controllers in your environment.
Prerequisite: Make sure you have the Windows Assessment and Deployment Kit (Windows ADK) and Windows PE installed. If not, download them here.
Figure 2: Providing the Windows ADK path.
Note: If the entered location is a shared path, select Authentication and provide the credentials of a user who can access the location.
RecoveryManager Plus can restore the backup of a domain controller to the same or a different physical machine. You can also use the product to restore the backup of a domain controller to a virtual machine.
Once the recovery media is created, follow the steps below for non-authoritative restoration of domain controllers.
Figure 5: Providing the location of your full backup (local path).
Figure 6: Providing the location of your full backup (network share).
Figure 7: Providing the credentials for accessing the network location.
Figure 9: Confirming the domain controller restoration process.
Figure 10: Domain controller restoration process completion and Restoration Summary.
To stop the restored domain controller from receiving changes via replication, and to make all the other domain controllers in the domain have the same state as the restored domain controller, perform an authoritative restoration by following the steps listed below.
Note: A domain controller can be authoritatively restored only after non-authoritative restoration is complete. Follow the steps listed in the previous section to complete non-authoritative restoration before proceeding with authoritative restoration.
Syntax: CN=value,OU=value,DC=value,DC=value.
Once restoration is complete, all domain controllers in the domain will be in the same state as the restored domain controller.
Fill this form, and we'll contact you rightaway.
Our technical support team will get in touch with you at the earliest."
RecoveryManager Plus is an excellent product. It has given us peace of mind that we can quickly recover should something happen to our AD
Our support engineers will get in touch with you shortly.