Tchater maintenant avec le support
Tchattez avec un ingénieur du 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 to create a virtual test environment

This section lists considerations, precautions, and provides step-by-step instructions for creating a new virtual test environment.

In this section:

 

Considerations

This section describes the various aspects you should consider before creating a new virtual test environment or opening an existing virtual lab project.

In this section:

 

Isolated virtual network and DNS

To ensure that the target virtual machine in the virtual lab does not affect the source environment, the target lab network must be isolated. Two levels of isolation can be applied:

  • At the virtual machine level

You can configure the IP subnet that is different from the source machine subnet. Please ensure that gateway doesn't provide connectivity to production subnet.

  • At the infrastructure level

There are several options to isolate network on the infrastructure level, some of them are:

  • Configure the standalone target host that has the standard virtual switch dedicated to the virtual lab and is not connected to the uplink physical adapter. This means that all target virtual machines can talk to each other, but cannot connect to the physical network or to virtual machines on other hosts. A virtual machine also cannot connect to virtual machines connected to a different virtual switch on the same host.

  • Configure isolated Virtual Local Area Network (VLAN) with standard/distributed virtual switch. In this configuration, the virtual machine is isolated through VLAN ID settings. Distributed virtual switch with VLAN ID settings is the recommended option to support the DRS cluster feature.

Recommendations and considerations related to the DNS server:

  • Add a DNS server to your virtual test environment. Ensure your virtual test environment has a properly configured DNS server. Add a source DNS server computer to your virtual lab project at Step 2: Add source computers to virtual lab project, so that the Active Directory Virtual Lab creates a virtual machine for the DNS server in your test environment.

  • Initially, use one DNS server per domain that hosts its DNS zone. We recommend that in Step 3: Modify virtual machine creation settings you specify the same DNS server for all target virtual machines in that domain. This does not mean that you should not add multiple DNS servers to your virtual test environment. You can add them, but initially configure the target virtual machines to use only one of the added DNS servers. After you start your virtual test environment and Active Directory® replication completes then you can reconfigure the target virtual machines to use other DNS servers you have added.

  • AD and DNS may be interdependent at startup. In case with Active Directory-integrated DNS, you should consider the fact that Active Directory and DNS are interdependent at startup. That is, when you start virtual machines in the virtual test environment, Active Directory® waits for DNS to become available. In turn, DNS cannot start without Active Directory®. However, there’s a timeout programmed in Active Directory®, and after some time of waiting Active Directory® starts without DNS, and this will make DNS work too.

  • Invalid resource records in DNS. If DNS in the virtual test environment is the exact copy of the source DNS and you excluded some source computers from the virtual test environment, there may be left some invalid resource records in DNS referring to those excluded computers. To eliminate the invalid resource records from DNS, recreate the primary forward lookup zones in your virtual test environment. As for invalid resource records in the reverse lookup zones, you can recreate or delete these zones because they are not vital for Active Directory®.

 

Virtualization agent behavior

To create virtual machines, the virtualization software supported by the Active Directory Virtual Lab needs to install its virtualization agent on the source computers.

Note

If you work with Microsoft SCVMM 2012 R2, use the Disk2vhd utility instead of virtualization agent. For more details, see Working with SCVMM 2012 R2.

If you use Microsoft SCVMM, it automatically removes its virtualization agent from the source computers after the virtualization completes. However, in case with VMware vCenter or ESX, the virtualization agent remains on the source computers after the virtualization. You can uninstall the agent manually by using a shortcut menu command on the source computers in the Active Directory Virtual Lab console.

 

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation