Chatta subito con l'assistenza
Chat con il supporto

Recovery Manager for AD Forest 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 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
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

VMware Environment

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 vCenter® Converter™ Server, Recovery Manager Console and VMware vCenter® / VMware ESX® Server.

If Active Directory Virtual Lab is unable to connect to VMware vCenter® Converter™ Server with the following errors, you should enable communication between VMware PowerCLI and VMware vCenter Server® systems that use the TLSv1.1 or TLSv1.2 protocols. For more details, see Enabling the TLSv1.1 and TLSv1.2 protocols for PowerCLI (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.

Resources/Images/8_UG.png

 

Support for VMware DRS Clusters

VMware DRS (Distributed Resource Scheduler) is a load balancing utility that assigns and moves computing workloads to available hardware resources in a virtualized environment. Active Directory Virtual Lab supports DRS clusters with Partly Automated or Fully Automated automation level.

  • Partly Automated

New virtual machine is placed on the best-suited host based on performance and resource criteria. If the DRS cluster becomes unbalanced, DRS will display recommendations for migration of the virtual machine.

  • Fully Automated

DRS places a virtual machine on the best-suited host, without prompting the user. If the DRS cluster becomes unbalanced, DRS will automatically migrate virtual machines.

Now in the ADVL console, you can specify a target host or a DRS cluster to create a virtual machine. For the DRS cluster, the target host will be selected automatically. The storage that is selected for the target virtual machine must be accessible from any host in the DRS cluster to successfully migrate the virtual machine.

The recommended network configuration for the DRS cluster is Distributed vSwitch connected to Virtual Local Area Network (VLAN). For more details, see the "network isolation at the infrastructure level" clause in Isolated virtual network and DNS.

If VLAN cannot be configured for the DRS cluster, you can use the host-only network configuration to ensure the network isolation. The host-only network configuration can be achieved by setting up virtual machine/host groups and affinity rules that allow you to disable the DRS cluster load balancing. To do so, create a host group that includes only one host and a virtual machine group that includes all virtual machines converted by Active Directory Virtual Lab. Then, you need to create a rule that assigns the virtual machine group to the host group using the affinity rule "Must run on hosts in group".

Recovery Manager for Active Directory provides an option to pause the lab creation process to perform all required actions before the virtual machine is turned on for the first time. To enable the pause option, set the HKLM\SOFTWARE\Wow6432Node\Quest\Recovery Manager for Active Directory\ADVL\PauseAfterCloning (DWORD) registry key to 1.

 

Deployment

By default, the Active Directory Virtual Lab is automatically installed when you install Recovery Manager for Active Directory. If necessary, you can exclude the Active Directory Virtual Lab from installation or uninstall it.

Important

To create virtual test environments, the Active Directory Virtual Lab requires third-party virtualization software. Make sure you have supported virtualization software installed and accessible to the Active Directory Virtual Lab. For a list of supported virtualization software, see the System Requirements section in the Release Notes.

To exclude Active Directory Virtual Lab from installation
  • Start the Recovery Manager for Active Directory Setup Wizard and use the Custom option to select the features you want to install.
To uninstall Active Directory Virtual Lab

  1. Open the list of installed programs (appwiz.cpl).

  2. In the list, select the Recovery Manager for Active Directory entry, and then click the Change button.

  3. Follow the steps in the Setup Wizard to change the installation so as to uninstall the Active Directory Virtual Lab feature.

 

User interface

The graphical user interface where you can manage the creation of a virtual test environment is called the Active Directory Virtual Lab console.

To start the Active Directory Virtual Lab console

From the Windows Server with Active Directory Virtual Lab installed

  1. Click Start.

  2. Point to All Programs | Quest| Recovery Manager for Active Directory.

  3. Click Active Directory Virtual Lab.

In this section:

 

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione