Chat now with support
Chat with Support

Quest has tools and processes in place to identify, protect, detect, and remediate vulnerabilities and incidents when they occur, including external security partners. As part of our standard security operations, Quest does not use CrowdStrike in any of our operations. We are reviewing our third parties, and so far, there is minimal affect. It is Quest's policy not to provide further technical details unless they directly impact customer data.

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

Step 1: Select a backup

  1. In the Recovery Manager Console tree (left pane), expand Backups, and select the AD LDS (ADAM) node.

  2. In the right pane, select the backup from which you want to restore AD LDS (ADAM) instance.

If the backup is not available in the right pane, on the main menu, select Action, point to Register Backup, and then click Register Backup File to browse for, select, and register the backup with RMAD.

 

Step 2: Restore AD LDS (ADAM) instance

  1. On the main menu, select Action | Online Restore, and step through the Online Restore Wizard for AD LDS (ADAM).

  2. On the Wizard Operation Mode page, select the Compare, restore, and report changes in AD LDS (ADAM) option. Click Next.

  3. On the AD LDS (ADAM) Instance Selection page, select the AD LDS (ADAM) instance you want to restore, and click Next.

  4. On the Backup Selection page, select the backup from which you want to restore the AD LDS (ADAM) instance, and step through the wizard to complete the restoration of the selected AD LDS (ADAM) instance.

 

Method 2: Restore an AD LDS (ADAM) database from a backup created with third-party software

Complete these steps:

 

Step 1: Extract and register AD LDS (ADAM) database

  1. Use the third-party backup software to extract the AD LDS (ADAM) database files from the backup to an alternate location. For more information, see the documentation supplied with the backup software you use.

  2. In the Recovery Manager Console tree (left pane), expand Backups, and select the AD LDS (ADAM) node.

  3. On the main menu, select Action, point to Register Backup, and then click Register Offline AD LDS (ADAM) Database to browse for, select, and register the .dit file and log files that belong to the AD LDS (ADAM) database you want to register with RMAD.

 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating