Create AD replication from backup media

There are usually two methods to restore the Active Directory database to the domain controller.

The traditional method is to use a new system as the domain controller, allowing normal replication programs to load the Active Directory data into the new system. Another method is to use the backup of the Active Directory database as the new domain controller.

The second method is faster, but it can only restore the active database to the State saved before backup. This may mean that the recovered system cannot be synchronized with several other domain controllers in the domain. The difference may be several hours, days, or weeks.

When recovering an Active Directory from a backup, you may consider whether to adopt a non-verification method or a verification method. Non-verified recovery allows the restored Domain Controller to be completely updated during subsequent replication. Verification recovery loads the data on the recovered domain controller to all other domain controllers.

The initial backup tool can be used to back up and restore the AD database, but it can only be used for non-verified recovery. To restore the AD database, the Active Directory must be offline. To recover the Active Directory database instead of performing verification, first start the domain controller to the directory service recovery mode and press the F8 startup key) and log on as a local administrator, then, use the backup tool to restore the system status to the original location for non-verified AD recovery.

There are only a few reasons for you to verify and recover. For example, accidentally deleting a target. If you delete the target by mistake, you need to verify and restore it. First, perform the same operations as non-validation recovery, and then specify the portion of the AD database that takes precedence over other new targets in the domain. The NTDSUTIL tool can effectively execute the second method.