Chat now with support
Chat mit 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

How does Recovery Manager for Active Directory isolate domain controllers during forest recovery?

The overall success of a domain or forest recovery operation very much depends on the domain controllers being restored from backups. Not only it is important to ensure these domain controllers are restored from recent and trusted backups, it is also necessary to temporarily isolate these domain controllers to guarantee that no dangerous or unwanted data will be replicated to them from their replication partners and to block requests to Active Directory® from client workstations during the recovery. Recovery Manager for Active Directory isolates domain controllers by creating a service dependency and using custom Internet Protocol security (IPSec) rules.

Before isolating the domain controllers being restored from backups, Recovery Manager for Active Directory backs up the IPSec settings existing in your environment to revert to these settings later.

Then, at the recovery step named Enable domain controller isolation, Recovery Manager for Active Directory does the following:

  1. Establishes a dependency between the IPsec Policy Agent (PolicyAgent) service and the Active Directory Domain Services (NTDS) service. As a result, the Active Directory Domain Services service cannot start until the IPsec Policy Agent service starts.

  2. Activates a number of custom IPSec rules defined in the IsolateDC.bat file.

The IsolateDC.bat file is located in the Recovery Manager for Active Directory installation folder (by default, this is %ProgramFiles%\Quest\Recovery Manager for Active Directory). The IPSec rules defined in the IsolateDC.bat file block all IP traffic between the domain controllers and their replication partners, except for the IP traffic generated by the following tools/services:

  • Remote Desktop Connection client

  • Ping command

  • File sharing services

  • Domain Naming System

These IPSec rules also apply to the IP traffic from the domain controllers to the Forest Recovery Console computer. Traffic from the Forest Recovery Console computer to the domain controllers is not affected by these IPSec rules.

Note

You can edit the IsolateDC.bat file to define the IPSec rules that become active during recovery. However, we cannot guarantee that problems that may occur if you incorrectly edit the IsolateDC.bat file can be solved. Edit the IsolateDC.bat file at your own risk.

At the recovery step named Ensure that domain controller isolation is disabled, Recovery Manager for Active Directory removes the dependency between the Active Directory Domain Services service and the NTDS service and uses the UnisolateDC.bat file to revert to the pre-recovery IPSec settings.

The UnisolateDC.bat file is located in the Recovery Manager for Active Directory installation folder (by default, this is %ProgramFiles%\Quest\Recovery Manager for Active Directory).

 

How does Recovery Manager for Active Directory select a DC to add the global catalog during forest recovery?

When recovering an Active Directory® forest, Recovery Manager for Active Directory adds the global catalog to the DCs that acted as global catalog servers before the recovery, provided that these DCs were successfully restored from backup.

If none of DCs that acted as global catalog servers before the recovery were successfully restored from backup, Recovery Manager for Active Directory adds the global catalog to the DC which was assigned the Schema Master role during the recovery.

 

Best practices for using Computer Collections

This section provides some recommendations for performing granular restore operations with Recovery Manager for Active Directory.

A Computer Collection allows you to group the computers (domain controllers or AD LDS (ADAM) hosts) to which you want to apply the same backup creation settings. For more information on how to create and manage Computer Collections, see the User Guide supplied with this release of Recovery Manager for Active Directory.

It is recommended to add computers to the same Computer Collection if you want to apply the same backup storage policy to all these computers.

For instance, you may want to store domain controller backups in one central location accessible to the Recovery Manager Console over a fast link. This scenario eliminates the need to copy the backups across the network before running an online restore operation and allows you to centrally manage the restore.

Set up the same backup creation schedule for all these computers. When scheduling backups for Computer Collections, it is important to consider that the performance of Recovery Manager for Active Directory may change depending on the number of Computer Collections and DCs in each Computer Collection. For example, the following table outlines the performance for different Computer Collection sizes.

note

These performance results were gathered from Recovery Manager for Active Directory with the following configuration:

  • Windows Server 2019

  • 4 vCPU, 8 GB RAM

  • Backup schedule configured for every Computer Collection

Table: Performance results for scheduled Computer Collections

RMAD configuration Metrics
Number of Computer Collections Number of DCs in each Computer Collection Console start time (seconds) Time to expand node (seconds) Time to add 1 collection (seconds) Time to remove 1 collection (seconds) Time to rename 1 collection (seconds)
10 10 1-2 <1 0 0 0
10 100 1-2 <1 0 0 0
50 10 2-3 1-2 0 0 0
50 100 2-3 1-2 0 0 0
100 10 4-5 3-4 0 0 0
100 100 4-5 3-4 0 0 0
500 10 21-22 20-21 1 0.5 0
500 100 25-26 23-24 2 0.7 0
1000 10 43-44 41-43 3 1.5 0
1000 100 43-44 42-44 5 2 0

The following diagram provides an example of using Computer Collections:

Figure: Example of Using Computer Collections

In this example, the Recovery Manager Console is installed in the London site. Computer Collections 1, 2, and 3 include all domain controllers from the Tokyo, London, and New York sites, respectively. Computer Collection 4 includes two domain controllers from the London site. Backups of these two domain controllers are accessible to the Recovery Manager Console via a fast link and can be used to perform selective online restores of Active Directory® objects.

 

Technical characteristics

This section provides some technical characteristics of the product.

 

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen