サポートと今すぐチャット
サポートとのチャット

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

Forcing replication

When you choose to force the replication, the wizard ensures that all linked attributes, such as group memberships, of the undeleted objects are correctly restored on all domain controllers.

This choice may result in considerable replication traffic, depending on the number of domain controllers in your domain. However, it is required because of the way links and deletions are dealt with in Active Directory®. Before the restoration of linked attributes, the undeleted objects must be replicated to all domain controllers for the restored linked attributes to be correctly represented on each domain controller.

This requirement stems not from the wizard’s implementation, but from the way in which the data is replicated in Active Directory®.

 

Skipping replication

When you choose not to force the replication, you may risk a loss of linked attributes, such as group memberships, on replication partners after the normal Active Directory® replication transfers the undeletion to all domain controllers.

For example, when you select a user to be undeleted, with the user being a member of a certain group, and choose not to have the wizard force the replication, the results of the restore on the representation of the user’s group memberships may vary. These variations are based on which objects replicate first after the wizard completes the restore.

If the undeletion of the user replicates first, then the group membership information of both the group (the members it contains) and the user (the groups he or she belongs to) will be represented correctly.

If the restore of the group replicates first, the replication partners will drop the addition of the (locally) deleted user from the group membership. The only exception to this is the user’s primary group, which is always represented correctly from both the user and group reference.

The wizard marks the undeleted objects so that they are replicated in a proper sequence. However, making changes to them before the replication is completed may break the proper sequence. Skip the replication enforcement if you are sure that no changes will be made to the restored objects until those objects are replicated to all domain controllers within the domain. Optionally, you may have the wizard force the incremental replication on the final step. You might also force the replication with a different tool, or wait for replication to occur on normal schedule.

In addition, you might skip the replication enforcement if you undelete objects whose deletions are not yet replicated within your domain. In that scenario, the objects in question are not marked as deleted on other domain controllers, which ensures the correct representation of linked attributes.

 

Stopping online restore

When you choose to stop the online restore operation, the wizard neither forces the replication nor restores linked attributes.

This choice implies that you wait until the undeleted objects are replicated to all domain controllers, and then restore those objects once more using the wizard. In that scenario, the second path of the wizard is used to restore the linked attributes on the undeleted objects. Stop the operation if the enforcement of replication in your domain is inadmissible for some reasons, but you want to be sure that linked attributes be represented correctly on all domain controllers.

 

Using agentless or agent-based method

When comparing or restoring Active Directory® objects with the Online Restore Wizard, you can choose whether to use LDAP functions only (Agentless method) or Online Restore Agent (Agent-based method).

Note that some AD DS and AD LDS (ADAM) object attributes cannot be restored by using Recovery Manager for Active Directory. For more information on these attributes, see Quest® Knowledge Base Article 59039 “List of AD DS and AD LDS object attributes that Recovery Manager for Active Directory cannot restore” at Quest Support.

The following table contains performance test results of agentless and agent-based restore operations on the machine running Windows Server® 2008 R2. The agent-based restore is performed by a single Restore Agent instance.

Configuration of the test lab:
  • Operating System: Windows Server® 2008 R2

  • CPU: 2 x Intel® Xeon® E5-2651 v2 1.8 GHz

  • RAM: 7.5 GB

Performance test results:
Agent-based restore

Number of objects - Required time

  • 1000 - 20 - 40 sec

  • 10000 - 04 - 06 min

  • 50000 - 23 - 34 min

Agentless restore

Number of objects - Required time

  • 1000 - 40 - 70 sec

  • 10000 - 06 - 10 min

  • 50000 - 30 - 50 min

 

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択