Chat now with support
Chat with Support

Recovery Manager for AD 10.0.1 - User Guide

Overview 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
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 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 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 Using Management Shell Collecting diagnostic data for technical support Using Recovery Manager for Active Directory Web Interface Appendices
Frequently asked questions 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

Computer Restart

Use this page to specify how to restart the target computer in Directory Services Restore Mode.

  • Manual restart. With this option, you must restart the target computer manually.
  • Automatic restart. Restarts the target computer remotely, using the startup parameters shown in the Boot option box. If you want to apply different startup parameters, use Manual restart. When performing the automatic restart, the wizard modifies the Computer Restart page, allowing you to abort the shutdown, if necessary.
  • Boot option. When you select the Automatic restart option, displays the startup parameters used to restart the target computer remotely. If you want to apply different startup parameters, use Manual restart.

To restart the computer in Directory Services Restore Mode manually

  1. Restart the computer, and press F8 when you are prompted to do so.
  2. On the menu, choose Directory Services Restore Mode, and then press ENTER.
  3. If you have multiple systems installed on the computer, choose the system installation you are recovering, and then press ENTER. You must choose the same installation as the one that was started when you launched the Repair Wizard.

To abort the computer shutdown

  • Click Abort Shutdown.

The Abort Shutdown button is available only during a 40-second grace period. The process of restarting the domain controller in Directory Services Restore Mode can take several minutes. The Current Status box allows you to examine the progress of the restart.

After the domain controller is started in Directory Services Restore Mode, the wizard displays the Select Account dialog box. You must specify the password of the Directory Service Restore Mode Administrator.

In the Select Account dialog box, you must supply the account name and password of the target computer local administrator (Directory Services Restore Mode Administrator). You must use the credentials of an account that is stored in the local security account (SAM) database. You cannot use the name and password of an Active Directory administrator. This is because Active Directory is offline, and account verification cannot occur. Rather, the SAM accounts database is used to control access to Active Directory on the local computer while Active Directory is offline.

Primary Restore of SYSVOL

Use this page to specify whether to perform a primary restore of SYSVOL. This window appears if the wizard fails to access the SYSVOL share on any domain controller within the domain.

The Perform a primary restore of the SYSVOL check box forces the wizard to perform a primary restore of SYSVOL.

To restore the SYSVOL data as the primary data

  • Select the check box in the Primary Restore of SYSVOL window.

If the domain controller being recovered is the only functioning domain controller in the domain, the SYSVOLdata must be restored as the primary data. As a result, a new replication service database is created by loading the data present under the SYSVOL on the local domain controller. A primary restore is the same as non-authoritative except that the restored SYSVOL is marked as Primary.

Only use this option when the SYSVOL data is lost on all the domain controllers in the domain. Do not select the Perform a primary restore of the SYSVOL check box if the SYSVOL shares exist on other operational domain controllers in the domain. This option is only intended for disaster recovery cases when all members of the SYSVOL replica set are lost. Setting a member as initial master when it has other members from which to synchronize may result in breaking the replication of the SYSVOL share.

Restore Process Start

This page provides an overview of the settings you have specified in the previous steps of the wizard. To start the operation, click Next. To review or change your settings, click Back.

Restore Progress

This page shows the progress of the operation. You can stop the operation by clicking Cancel.

Clicking the Cancel button when the restore is in progress can result in serious, unexpected consequences that can prevent the system from starting and require that you reinstall the system.

Related Documents