To use this approach, you must have recent and trusted backups for as many domain controllers as possible in each domain in the forest. These backups must be created at a similar point in time to mitigate the risk of discrepancy after the forest is recovered.
At a high level, Approach 1 includes the following stages:
Recovery Manager for Active Directory restores as many domain controllers as possible in each domain from the recent and trusted backups you specify. The more domain controllers you restore from backups, the faster the forest recovery operation completes.
Recovery Manager for Active Directory uses Microsoft tools (Dcpromo.exe or the Uninstall-ADDSDomainController and Install-ADDSDomainController cmdlets) to automatically reinstall Active Directory on the domain controllers for which no backups are available.
The domain controllers where Active Directory was reinstalled replicate AD data from the domain controllers restored from reliable backups.
Approach 1 has the following advantages and limitations:
Fast recovery of the entire forest. Since most domain controllers are simultaneously restored from backups, the forest recovery operation completes faster than in Approach 2.
Stability of the forest recovery process. Owing to the large number of backups used, the entire forest is recovered even if the restore of some domain controllers fails.
This approach allows you to retain the original forest infrastructure. Since many domain controllers are restored from backups, the recovered forest is close to its original prefailure condition.
The risk of reintroducing corrupted or unwanted data is higher than in Approach 2. Because of the large number of backups used in this Approach, there is no guarantee that corrupted or unwanted data from the backups will not be reintroduced into the recovered forest.
For a step-by-step procedure on how to perform a forest recovery, Overview of steps to recover a forest
This recovery approach is recommended by Microsoft in the Planning for Active Directory Forest Recovery paper. To use this approach, you must have a recent and trusted backup for one domain controller in each domain in the forest. These backups must be created at a similar point in time to mitigate the risk of discrepancy after the forest is recovered.
At a high level, recovering a forest using this approach includes the following stages:
Recovery Manager for Active Directory restores one domain controller in each domain from the recent and trusted backup you specify.
Recovery Manager for Active Directory uses Microsoft tools (Dcpromo.exe or the Uninstall-ADDSDomainController and Install-ADDSDomainController cmdlets) to automatically reinstall Active Directory on the domain controllers for which no backups are available.
The domain controllers on which Active Directory was reinstalled replicate Active Directory data from the domain controllers restored from reliable backups.
Approach 2 has the following advantages and limitations.
Recommended by Microsoft. This recovery approach is recommended in the Microsoft’s bestpractice paper, Planning for Active Directory Forest Recovery.
Safer, healthier recovery as compared to Approach 1. The limited number of backups used in Approach 2 (one backup per each domain) allows you to check them all to make sure they do not include any corrupted or unwanted data.
Forest recovery may require significant time to complete. Approach 2 requires more time to complete than Approach 1.
Recovery of entire domain depends on a successful restore of a single domain controller. A successful restore of one domain controller from backup is required before Active Directory can be reinstalled on all other domain controllers in the domain.
The original forest infrastructure is not retained. Because Active Directory is reinstalled on most domain controllers in the forest, the forest infrastructure cannot be restored to its exact pre-failure state.
For a step-by-step procedure on how to perform a forest recovery, Overview of steps to recover a forest
To restore domain controllers from RMAD or BMR backups, use the backups that were taken a few days before the occurrence of the failure. In general, you have to trade off between recentness and safeness of restored data. Choosing a more recent backup recovers more useful data, but it might increase the risk of re-introducing dangerous data into the restored forest.
It is strongly recommended that you keep detailed logs about the health state of Active Directory on a daily basis, so that in case of a forest-wide failure you could identify an approximate time of the failure.
For more information on the methods you can use to select backups for recovery, see Selecting backups for recovery.
You can configure Recovery Manager for Active Directory to automatically run your custom scripts on the Recovery Manager for Active Directory computer before, after, or during the recovery operation.
Recovery Manager for Active Directory is supplied with a Microsoft Windows Script (.wsf) file serving as a template where you can insert your custom scripts written in the VBScript or JScript language. The file name is ConsoleSideScripting.wsf, and you can find it in the Recovery Manager for Active Directory installation folder (by default, this is %ProgramFiles%\Quest\Recovery Manager for Active Directory).
The .wsf file has a number of XML elements where you can insert your scripts. Each XML element in the .wsf file provides a description explaining when the script inserted that element will run. Depending on where you inserted your script, it will run:
Before the recovery operation starts in the current project.
Each time before the restore from backup operation starts on a domain controller in the current project.
After the restore from backup operation completes on all domain controllers in the current project.
Before the reinstall Active Directory operation starts in the current project.
Each time before the reinstall Active Directory operation starts on a domain controller in the current project.
Each time the reinstall Active Directory operation completes on a domain controller in the current project.
After the recovery operation completes in the current project.
Locate the file ConsoleSideScripting.wsf in the Recovery Manager for Active Directory installation folder, and open the file in a text editor.
In the file, read the descriptions provided for the XML elements to identify the ones where you want to insert your script, then insert your script as appropriate.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center
