Chat now with support
Chat with Support

Recovery Manager for AD Disaster Recovery Edition 10.0.1 - User Guide

Overview Backing up data
Permissions required for the Backup operation Managing Backup Agent Using a least-privileged user account to back up data Creating backups 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 Getting started
Permissions required to use Recovery Manager for Active Directory Recovery Manager Console Icons in the user interface Getting and using help Configuring Windows Firewall Using Computer Collections Managing Recovery Manager for Active Directory configuration Licensing
Restoring data
Getting started with Active Directory recovery Managing deleted or recycled objects Restoring backed up System State components 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
Fault tolerance Consolidating backup registration data Monitoring Recovery Manager for Active Directory Recovering an Active Directory forest
Permissions required to use Forest Recovery Console Forest Recovery Console Managing a recovery project Install Active Directory from Media recovery method Install Active Directory recovery method Managing Forest Recovery Agent Rebooting domain controllers manually Specifying fallback IP addresses to access a domain controller Resetting DSRM Administrator Password Purging Kerberos Tickets Managing the Global Catalog servers Managing FSMO roles Manage DNS Client Settings Configuring Windows Firewall Forest recovery overview 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
Bare metal forest recovery Using Management Shell Creating virtual test environments Using Recovery Manager for Active Directory web interface Appendices
Frequently asked questions Best practices for creating backups for forest recovery Best practices for recovering a forest Descriptions of recovery or verification steps 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

Communication ports

This section provides information about the communication ports required to create a virtual test environment with the Active Directory Virtual Lab.

In this section:

Microsoft SCVMM 2012/2012 SP1

Microsoft SCVMM 2012 or 2012 SP1 Environment

Microsoft SCVMM 2012 R2/2016

Microsoft SCVMM 2012 R2 or 2016 Environment

VMware Environment

NOTE:

  • To successfully setup the VMware vCenter Converter Agent you should provide network connections via DNS between all members of the conversion process: domain controller, VMware Converter Server, Recovery Manager Console and VMware vCenter/ESX Server.
  • If Active Directory Virtual Lab is unable to connect to VMware Converter Server with the following errors, you should enable communication between PowerCLI and vCenter Server systems that use the TLSv1.1 or TLSv1.2 protocols. For more details, see https://kb.vmware.com/s/article/2137109.

    • "Unable to establish a secure communication channel between the converter server and the remote machine"

      -OR-

    • "Could not access the VMware vCenter Converter server. Details: The underlying connection was closed: An unexpected error occurred on a send"

  • To install Converter Agent, use built-in Administrator account to connect to the source machine or disable User Access Control (UAC) on the source machine.

Related Documents