Chat now with support
Chat with Support

Recovery Manager for AD Disaster Recovery Edition 10.2.2 - 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 Cloud Storage Secure Storage Server Hybrid Recovery with On Demand Recovery 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 method Bare metal forest recovery Using Management Shell Creating virtual test environments 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

Revoking licenses

When the actual number of user accounts exceeds the licensed number, Recovery Manager for Active Directory (RMAD) returns a warning message each time you back up data. In this case, you can revoke licenses from the domains whose backups you no longer need. The revoked licenses are returned to the pool of available licenses and you can allocate them to a different domain.


When you revoke licenses from a domain, all backups created by RMAD for that domain get deleted. You should only revoke licenses from a domain if you no longer need backups created for that domain.

To revoke licenses from a domain
  1. In the console tree, right-click the root node, and then click About.

  2. In the About dialog box, click the License tab.

  3. On the License tab, select the domain from the License Usage list, and then click Revoke.

  4. In the confirmation message box, click Yes.


Backing up data


Permissions required for the Backup operation

The table below lists the minimum user account permissions required to perform the Backup operation.

Minimum permissions required for the Backup operation

Backing up the AD data using the preinstalled Backup Agent

Membership in the RMAD Backup Operators group.


Builtin\Backup Operators domain local group.

Create the RMAD Backup Operators group before the Backup Agent installation. For more details, refer to Using a least-privileged user account to back up data.

If the Ensure Forest Recovery Agent is deployed check box is selected on the Agent Settings tab of the backup collection Properties, the account must be added to the Builtin\Administrators domain local group.

Backing up the AD data using the automatically installed Backup Agent

Membership in the Builtin\Administrators domain local group.

This operation is always performed under the Recovery Manager Console account.

Installing the Backup Agent

Membership in the Builtin\Administrators domain local group.


Domain Admins group.


Managing Backup Agent

Recovery Manager for Active Directory (RMAD) employs a Backup Agent to back up data on domain controllers and AD LDS (ADAM) hosts added to Computer Collections. For this reason, the Backup Agent must be installed on each computer where you plan to back up data by using RMAD.

For each Computer Collection, you can specify whether you want to use only preinstalled instances of Backup Agent or want to automatically install Backup Agent when necessary. You can configure RMAD in one of the following ways:

  • Use preinstalled Backup Agent only. When configured this way, RMAD will only use the Backup Agent you manually preinstalled on the computers in the Computer Collection.

  • Use preinstalled Backup Agent and automatically install the agent when necessary. With this method, RMAD will use preinstalled Backup Agent if it is present on the target computer. If the Backup Agent is missing, RMAD will automatically install it before backing up data on the target computer, and then will automatically remove the automatically installed agent upon the backup operation completion.

You can specify one of these methods in the Computer Collection properties. For more information, see Agent Settings tab subsection in Properties for an existing Computer Collection.

In this section:


Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating