Chat now with support
Chat with Support

Recovery Manager for AD Disaster Recovery Edition 10.3 - 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

Best practices for recovering a forest

 

How many Instances of the Forest Recovery Console to deploy?

The Forest Recovery Console must have access to the Recovery Manager for Active Directory backup registration database containing information about all backups of the domain controllers in the forest. To meet this requirement, you must deploy the Forest Recovery Console on the same computer that hosts the Recovery Manager Console used to create backups of the domain controllers.

You can easily meet this requirement in simple and relatively small environments where you have a single instance of the Recovery Manager Console deployed. However, in complex and large environments the requirement to have a single instance of the Recovery Manager Console (and thus maintain a single forest-wide backup registration catalog) might not be feasible.

For more information on how to consolidate backups created by different instances of Recovery Manager for Active Directory deployed in your environment, see Consolidating backups from different backup registration databases.

 

Where to Install the Forest Recovery Console?

The best practice is to install the Forest Recovery Console on a standalone computer. This allows you to avoid situations where a corruption in Active Directory® prevents you from using the Forest Recovery Console.

 

Backing up the Recovery Manager for Active Directory configuration

It is recommended to regularly back up the Recovery Manager for Active Directory (RMAD) configuration, so that you could quickly reinstall the product and restore its configuration to the last backed up state in case RMAD becomes inoperable due to a failure. All the RMAD configuration data is held in the following location on the RMAD computer: %AllUsersProfile%\Quest\Recovery Manager for Active Directory. The Recovery Manager Console saves its configuration data in the following files:

  • Rmad.db3. Contains the Recovery Manager Console configuration data, such as computer collections and backup creation sessions.

  • Backups.mdb. Contains the backup registration database that stores information about created Active Directory® and AD LDS (ADAM) backups.

As a rule, the overall size of these .mdb files does not exceed 10 MB.

The Forest Recovery Console saves all its configuration data in the Forest Recovery Project (.frproj) file.

 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating