Chatee ahora con Soporte
Chat con el soporte

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

Opening a legacy virtual lab project

Recovery Manager for Active Directory supports only legacy ADVL projects that were created with Active Directory Virtual Lab 9.x or later.

Now Active Directory Virtual can open a legacy Virtual Lab Project (.vlproj) file if FIPS-compliant algorithms are enabled on the Active Directory Virtual Lab computer.

Note

To protect its data, the Active Directory Virtual Lab 9.x or later uses the SHA-1 hashing algorithm and the Triple DES encryption algorithm that are FIPS-compliant. For more information about FIPS-compliant algorithms, see Microsoft Knowledge Base article 811833 “The effects of enabling the ‘System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing’ security setting in Windows XP and in later versions of Windows” at https://support.microsoft.com.

 

Precautions

Please consider the following precautions before creating a virtual test environment:

  • Virtual test environments created by the Active Directory Virtual Lab can only be used for testing, training, or evaluation purposes. Never restore or copy any data from your virtual test environments to the production Active Directory®.

  • Ensure your virtual test environment is properly isolated from the source Active Directory® forest. Otherwise, the source forest may be seriously damaged after you enable the network adapters in the newly-created virtual test environment.

 

Step-by-step instructions

To create a virtual test environment from an Active Directory® forest, complete these steps:

 

Step 1: Create a virtual lab project

To create a virtual lab project

  • Start the Active Directory Virtual Lab console.

    After the console opens, a wizard starts automatically to guide you through the virtual lab project creation.

    Alternatively, if you have the Active Directory Virtual Lab console already open, from the main menu, select File | New Project, and then follow the steps in the wizard.

When creating a virtual lab project, you are prompted to specify the following:

  • Third-party virtualization software with which to create virtual machines from the source computers.

    The virtualization software must be preinstalled in your environment and be accessible to the Active Directory Virtual Lab. For the privileges required to use the virtualization software, see Permissions.

  • Source Active Directory forest from which to create your virtual test environment.

  • Default hardware settings for creating virtual machines from source computers in the virtual lab project.

If necessary, you can modify these default settings for each virtual machine to be created.

  • A Virtual Lab Project (*.vlproj) file to save your project. You can reuse the settings stored in the .vlproj file to create more virtual test environments in the future.

 

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación