Chat now with support
Chat with Support

Recovery Manager for AD Disaster Recovery Edition 10.1 - User Guide

Overview Getting started
Permissions required to use Recovery Manager for Active Directory Recovery Manager Console Getting and using help Configuring Windows Firewall Using Computer Collections Managing Recovery Manager for Active Directory configuration Licensing
Backing up data
Permissions required for the Backup operation Managing Backup Agent Using a least-privileged user account to back up data Using Managed Service Accounts Active Directory backups vs Windows System State backups Creating BMR and Active Directory backups Using the Backup Wizard Retrying backup creation Enabling backup encryption Backing up AD LDS (ADAM) Backing up cross-domain group membership Backing up distributed file system (DFS) data Backup scheduling Setting performance options Setting advanced backup options Using Forest Recovery Agent Unpacking backups Using e-mail notification Viewing backup creation results
Restoring data
Getting started with Active Directory recovery Managing deleted or recycled objects Restoring backed up Active Directory components Integration with Change Auditor for Active Directory Using granular online restore Restoring AD LDS (ADAM) Selectively restoring Active Directory object attributes Restoring objects in an application directory partition Restoring object quotas Restoring cross-domain group membership Performing a restore without having administrator privileges Reports about objects and operations Using complete offline restore Offline restore implications Restoring SYSVOL authoritatively Performing a granular restore of SYSVOL Recovering Group Policy Restoring data from third-party backups Using the Extract Wizard Restoring passwords and SID history
Full Replication Consolidating backup registration data Monitoring Recovery Manager for Active Directory Recovering an Active Directory forest
Forest recovery overview Deploying Recovery Manager for Active Directory Forest Edition (Disaster Recovery Edition) Permissions required to use Forest Recovery Console Forest Recovery Console Managing a recovery project Recovery methods Phased recovery Managing Forest Recovery Agent Rebooting domain controllers manually Resetting DSRM Administrator Password Purging Kerberos Tickets Managing the Global Catalog servers Managing FSMO roles Manage DNS Client Settings Configuring Windows Firewall Developing a custom forest recovery plan Backing up domain controllers Assigning a preferred DNS server during recovery Handling DNS servers during recovery Forest recovery approaches Deciding which backups to use Running custom scripts while recovering a forest Overview of steps to recover a forest Viewing forest recovery progress Viewing recovery plan Viewing a report about forest recovery or verify settings operation Handling failed domain controllers Adding a domain controller to a running recovery operation Selectively recovering domains in a forest Recovering SYSVOL Deleting domains during recovery Resuming an interrupted forest recovery Recovering read-only domain controllers (RODCs) Checking forest health Collecting diagnostic data for technical support
Restore Active Directory on Clean OS Bare metal forest recovery Using Management Shell Creating virtual test environments Using Recovery Manager for Active Directory web portal Appendices
Frequently asked questions Best practices for using Computer Collections Technical characteristics Best practices for creating backups Best practices for creating backups for forest recovery Best practices for recovering a forest Descriptions of recovery or verification steps Ports Used by Recovery Manager for Active Directory Forest Edition (Disaster Recovery Edition) Backup Wizard Online Restore Wizard Online Restore Wizard for AD LDS (ADAM) Group Policy Restore Wizard Repair Wizard Extract Wizard Events generated by Recovery Manager for Active Directory Descriptions of PowerShell commands
Add-RMADBackup Add-RMADCollectionItem Add-RMADFEComputer Add-RMADReplicationConsole Add-RMADStorageServer Backup-RMADCollection Close-RMADFEProject Compare-RMADObject Convert-RMADBackup ConvertTo-RMADRecycledObject Create-RMADStorageManagementAgentSetup Expand-RMADBackup Export-RMADBackup Export-RMADFERecoveryCertificate Export-RMADFEResult Get-RMADBackup Get-RMADBackupAgent Get-RMADBackupInfo Get-RMADBackupObject Get-RMADBackupSecurityStatus Get-RMADCollection Get-RMADCollectionItem Get-RMADDeletedObject Get-RMADFEComputer Get-RMADFEConsole Get-RMADFEDnsCache Get-RMADFEDomain Get-RMADFEEvent Get-RMADFEGlobalOptions Get-RMADFEOperation Get-RMADFEPersistenceConnection Get-RMADFEProject Get-RMADFERecoveryAgent Get-RMADFESchedule Get-RMADGlobalOptions Get-RMADLicenseInfo Get-RMADObject Get-RMADReplicationConsole Get-RMADReplicationSchedule Get-RMADReplicationSession Get-RMADReplicationSessionItem Get-RMADReportObject Get-RMADReportObjectAttributes Get-RMADReportObjectChildren Get-RMADReportSession Get-RMADSession Get-RMADSessionItem Get-RMADSessionItemEvent Get-RMADStorageServers Import-RMADBackup Import-RMADFERecoveryCertificate Install-RMADBackupAgent Install-RMADFERecoveryAgent New-RMADCollection New-RMADFEProject New-RMADFERecoveryMedia New-RMADSchedule Open-RMADFEProject Publish-RMADBackupSecurityStatus Remove-RMADBackup Remove-RMADBackupAgent Remove-RMADCollection Remove-RMADCollectionItem Remove-RMADFEComputer Remove-RMADFERecoveryAgent Remove-RMADFESchedule Remove-RMADReplicationConsole Remove-RMADReplicationSchedule Remove-RMADReplicationSession Remove-RMADStorageServer Remove-RMADUnpackedComponent Rename-RMADCollection Restore-RMADDeletedObject Restore-RMADDomainController Restore-RMADObject Resume-RMADFERecovery Save-RMADFEProject Set-RMADCollection Set-RMADFEComputer Set-RMADFEDnsCache Set-RMADFEDomain Set-RMADFEGlobalOptions Set-RMADFEPersistenceConnection Set-RMADFERecoveryMode Set-RMADFESchedule Set-RMADGlobalOptions Set-RMADReplicationConsole Set-RMADReplicationSchedule Start-RMADFERecovery Start-RMADFEVerification Start-RMADReplication Start-RMADReportViewer Stop-RMADFEWorkflow Update-RMADBackupAgent Update-RMADFEProject Update-RMADLicense

Recovering SYSVOL

Recovery Manager for Active Directory supports authoritative restore of SYSVOL on the selected domain controllers. Authoritative SYSVOL restores are used in case of critical situations such as divergence of data in the content of the SYSVOL share.


  • If you have very large backups and the backup data is stored on a remote computer (not on domain controllers), you do not need to specify the backups for non-authoritative domain controllers in Forest Recovery Console to restore the SYSVOL data. When the backup is not selected, the SYSVOL data is replicated from the authoritative domain controller by the replication service. In this case, the full backup information is not copied to the domain controller that saves the disk space.

  • Along with the SYSVOL restore, Recovery Manager for Active Directory allows you to perform the non-authoritative restore of RODCs using the Restore SYSVOL recovery method.

To restore the SYSVOL folder from backup, perform the following steps
  1. Open your recovery project where the authoritative restore of SYSVOL will be performed.

  2. On the menu bar, click Tools | Recovery Project Settings.

  3. Open the Recovery Mode tab.

  4. In the Recovery scope drop-down list, select SYSVOL Recovery. If the SYSVOL Recovery scope is selected, the Restore SYSVOL method is set on the General tab in the domain controller recovery settings and cannot be changed.

  5. Select the check boxes next to the domains you want to recover and specify a domain controller for each domain to perform the authoritative restore. If the domain controller is not specified, it will be selected automatically. For more information, see How does Recovery Manager for Active Directory select a DC for an authoritative (primary) restore of SYSVOL during forest recovery.

  6. Optionally, you can specify default credentials to access domain controllers in the selected domains.

  7. Click OK.


Deleting domains during recovery

When recovering an Active Directory forest, you can use Recovery Manager for Active Directory to selectively delete particular domains from the forest being recovered. You may need to delete domains when, for example, the account you use to recover an Active Directory forest does not have sufficient permissions to access and recover some domains in the forest. In this case, you may want to sacrifice these domains and recover the forest without them.


  • You cannot selectively recover domains and delete domains at the same time. During recovery, use only one of these two features. For more information about selectively recovering domains, see Selectively recovering domains in a forest.

  • You cannot delete the root domain of the forest being recovered.

To delete a domain from the forest being recovered, you need to set the recovery method for all DCs in that domain to Do not recover. Then, after you run the recovery operation, Recovery Manager for Active Directory does the following:

  • Deletes the domain’s partition.

  • Cleans up metadata of all DCs in the domain from the forest.

To delete a domain while recovering an Active Directory forest
  1. In the Forest Recovery Console, open or create a recovery project.

  2. Set the recovery method for all DCs in the domain you want to delete to Do not recover:

    1. Select a DC in the list.

    2. On the General tab, from the Recovery method list, select Do not recover.

  3. Specify other settings for your recovery project as appropriate, and then click Start Recovery on the toolbar.


Resuming an interrupted forest recovery

Recovery Manager for Active Directory provides the Fault Tolerance feature that allows you to resume the last forest recovery operation in case it was unexpectedly interrupted by one of these events:

  • You close the Forest Recovery Console while the forest recovery operation is still running.

  • The Forest Recovery Console unexpectedly shuts down partway through the forest recovery operation.

  • The computer running the Forest Recovery Console powers off while the forest recovery operation is still running.


The Fault Tolerance feature does not allow you to resume a forest recovery operation you canceled from the Forest Recovery Console (for example, by clicking the Abort button).

When the Fault Tolerance feature is enabled, it constantly saves the current forest recovery operation state to a dedicated SQL Server database named ForestRecovery-Persistence. Each time you start the Forest Recovery Console, a check is performed to see whether the last forest recovery operation was interrupted by any of the events listed earlier in this section. If that is true, the Forest Recovery Console prompts you to resume the forest recovery from the point at which it was interrupted.


If you chose to reset password for domain users in privileged groups when you started a forest recovery, you need to do it again when you resume the forest recovery because the console does not store passwords. However, if the password resetting was already completed for a domain controller before the recovery was interrupted, the passwords will not be reset again for the domain controller after you resume the operation.

In case you choose not to resume an interrupted forest recovery operation and select the Delete last recovery session data option in the Resume Recovery wizard, the saved session state will be permanently deleted from the ForestRecovery-Persistence database.

Permissions required to access the ForestRecovery-Persistence database
  • Add an account that is used to access the ForestRecovery-Persistence database as the Security Login in SQL Server Management Studio. The public role will be automatically granted to the user account on the Server Roles tab of Login Properties.

  • Add users mapped to this Login and assign the db_datareader role on the User Mapping page of the Login Properties to use the account as the Forest Recovery project reader.

  • Explicitly grant the Execute right on the Permissions tab of the ForestRecovery-Persistence database Properties.This permits to use the account for the Restore operation.

For the Fault Tolerance feature, all involved console instances must have the same communication keys that is used to communicate with Forest Recovery Agents without using the domain access credentials.

To share secure communication keys between console instances
  1. Open or create a recovery project in Forest Recovery Console.

  2. On the menu bar, select Tools | Fault Tolerance.

  3. Click Export secure communication keys… and specify the "secure communication keys" file location and access credentials.

  4. Save the "secure communication keys" file.

  5. Then, launch another instance of Forest Recovery Console.

  6. On the menu bar, select Tools | Fault Tolerance | Import secure communication keys…, specify the "secure communication keys" file and click Open.

  7. Reinstall the agents if they were uninstalled.

  8. For security reasons, remove the "secure communication keys" file from your computer after the Fault Tolerance feature will be configured.

To modify the fault tolerance settings for a recovery project
  1. In Forest Recovery Console, select Tools | Fault Tolerance | Settings from the toolbar.

  2. In the Fault Tolerance Settings dialog, use the following options:

Recovery persistence settings
Enable fault tolerance

Allows you to enable or disable the Fault Tolerance feature by selecting or clearing this check box.

SQL Server name and instance

Allows you to specify the SQL Server instance in which you want to store the current forest recovery operation state. To specify a SQL Server instance, use the format <SQLServerName>/<Instance>. The forest recovery operation state is saved to a SQL Server database named ForestRecovery-Persistence. If the ForestRecovery-Persistence database does not exist in the SQL Server instance you specify, it will be created there. If the ForestRecovery-Persistence database already exists in the SQL Server instance you specify, the data in that database will not be erased until you start a new forest recovery operation. Until that moment, you can resume the interrupted forest recovery operation whose state is held in the specified ForestRecovery-Persistence database.

Authentication method

Allows you to select a method for authenticating on the specified SQL Server.

  • Use Windows authentication. Allows you to authenticate with the user account under which the Forest Recovery Console is currently running.

  • Use SQL authentication. Allows you to authenticate with the user name and password specified in this option. This authentication method is recommended when Recovery Manager for Active Directory uses the ForestRecovery-Persistence database that is hosted on an external SQL Server computer and not on the computer where Recovery Manager for Active Directory is running.

List of consoles

Shows the list of Forest Recovery Consoles configured to support the Fault Tolerance feature.


Recovering read-only domain controllers (RODCs)

Recovery Manager for Active Directory supports recovering read-only domain controllers (RODCs) from backups.

The full list of recovery methods that can be applied to the RODCs in your recovery project:

  • Restore SYSVOL

    This method allows you to perform the non-authoritative restore of RODCs

  • Reinstall Active Directory or Reinstall Active Directory from Media on the RODCs

  • Install Active Directory or Install Active Directory from Media on the RODCs

  • Uninstall Active Directory from the RODCs.

  • Do not recover the RODCs.

If you want to recover a read-only DC, you need to select the Install the domain controller as a read-only option on the General tab for the Install Active Directory (with IFM option) or Reinstall Active Directory (with IFM option) method in Forest Recovery Console. A read-only DC can be installed using a backup created only from the RODC.
Depending on whether the option is selected or not, you can only choose backups that DC Type corresponds to the type of domain controller (ReadOnly, Writable).


DC Type of backups that were created in the version 10.0 or earlier, and was registered manually, will be shown as Unknown. Such backups can only be selected manually, and the user must make sure that the type of domain controller being restored matches the type of domain controller for which the backup was created, otherwise, recovery of the domain controller will fail.


Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating