Chat now with support
Chat with Support

Recovery Manager for AD Disaster Recovery Edition 10.0.1 - User Guide

Overview 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 Using Forest Recovery Agent Unpacking backups Using e-mail notification Viewing backup creation results 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
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 Recovering an Active Directory forest
Permissions required to use Forest Recovery Console Forest Recovery Console Managing a recovery project Install Active Directory from Media recovery method Install Active Directory recovery method Managing Forest Recovery Agent Rebooting domain controllers manually Specifying fallback IP addresses to access a domain controller Resetting DSRM Administrator Password Purging Kerberos Tickets Managing the Global Catalog servers Managing FSMO roles Manage DNS Client Settings Configuring Windows Firewall Forest recovery overview 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
Bare metal forest recovery Using Management Shell Creating virtual test environments Using Recovery Manager for Active Directory web interface Appendices
Frequently asked questions Best practices for creating backups for forest recovery Best practices for recovering a forest Descriptions of recovery or verification steps 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

Preserving passwords and SID history in object tombstones

To preserve passwords and SID history in object tombstones, complete the following steps:

Step 1: Make sure prerequisites are met

  • You are logged on as a member of the Schema Admins group.
  • Write operations to the schema are allowed.

Step 2: Modify the searchFlags attribute value

To preserve SID History in tombstones, you need to modify the searchFlags attribute value for the SID-History (sIDHistory) schema object.

To preserve passwords in tombstones, you need to modify the searchFlags attribute value for the following password-related schema objects:

  • Unicode-Pwd (unicodePwd)
  • DBCS-Pwd (dBCSPwd)
  • Supplemental-Credentials (supplementalCredentials)
  • Lm-Pwd-History (lmPwdHistory)
  • Nt-Pwd-History (nTPwdHistory)

IMPORTANT: The Lm-Pwd-History and Nt-Pwd-History attributes are used to store password history. For security reasons, it is recommended to restore them along with the password.

To determine the new searchFlags attribute value to be set, use the following formula:

8 + current searchFlags attribute value = new searchFlags attribute value

To modify the searchFlags attribute value

  1. Use the ADSI Edit tool (Adsiedit.msc) to connect to the Schema naming context using the domain controller that holds the Schema Master FSMO role:
    1. Start the ADSI Edit tool (Adsiedit.msc).
    2. In the left pane of the console, right-click the ADSI Edit console tree root, and then on the shortcut menu click Connect to.
    3. In the dialog box that opens, do the following:
      • Click Select a well known Naming Context option, and then select Schema from the list below.
      • Click Select or type a domain controller or server option, and then type the name of the domain controller that holds the Schema Master FSMO role.
    1. Click OK to connect.
  2. In the left pane of the console, expand the Schema container to select the container that includes the schema objects you want to modify.
  3. Right-click the object you want to modify in the right pane, and then click Properties.
  4. Enter the new searchFlags attribute value you determined earlier:
  1. On the Attribute Editor tab, select searchFlags from the Attributes list, and then click the Edit button.
  2. In the Attribute Editor box, enter the new value and click OK.

Fault tolerance

Recovery Manager for Active Directory provides an ability to switch from the master Recovery Manager Console to the alternate instance of the console in case of any system failure, e.g. hardware failure. The Full Replication feature lets you create a full copy of the master console settings on the slave console, so that the slave console can fully take over the master console and perform exactly the same operations.

This functionality is based on the Recovery Manager Remote API Access service and PowerShell commands. The Recovery Manager Remote API Access service is an optional feature and must be selected when installing Recovery Manager for Active Directory Disaster Recovery Edition version 10.0.1. When the fault tolerance feature is enabled, the current console connects to the Recovery Manager Remote API Access service on the remote RMAD console, then imports the data , e.g. collection information, backup schedule task information, backup information, etc.

NOTE: The TCP port 52132 is required for Recovery Manager Remote API Access service.

Which settings are replicated?

  • Global settings
  • Computer collection settings, including the retention policy setting
  • Computer collections
  • Backup schedule task

    NOTE:

    • If the user account is a domain user or local user, it will be changed to "SYSTEM".
    • If the user account is Managed Service Account (in Windows Server 2008 or higher) or Group Managed Service Account (in Windows Server 2012 or higher), make sure that the account works in the current console. Otherwise, it will be changed to "SYSTEM" too.
    • All backups schedules are disabled after the replication.
  • Backup information
    • Backup information only, not the backup files.
    • If the path of backup is an absolute path ( e.g. "C:\backups\b1.bkf", it will be changed to the UNC path (e.g. "\\CurrentConsoleName\C$\ backups\b1.bkf").

Configure the full replication in Recovery Manager Console

This section describes how to create a full copy of the master console settings on the local instance of Recovery Manager Console and switch to the local console in case of the master console failure.

IMPORTANT:

  • It is recommended to use the full replication between consoles in the same datacenter to quickly switch to the slave console in case of the master console goes down.
  • Single-master mode: you can add several remote consoles to the replication list, but only one remote (master) console can be used for replication.
  • All local data (collections, collection properties, etc) is completely rewritten by the data from the master console.
  • After the replication, data on the slave console is read-only, but you can perform the compare and restore operations using this console.
  • It is recommended that you schedule the backup tasks and the replication task so that they do not overlap.

To add a remote (master) console to the local (slave) console and force the replication

  1. Open the local Recovery Manager for Active Directory console.
  2. Right-click Remote Consoles under the Replication node and select Add Console.
  3. In the Add Replication Console dialog, specify a host name where the RMAD console that will be used as a replication source is installed.
  4. Select Replicate backup information, collections, global settings and schedule(Full mode).
    This option lets you create the full copy of the master console on the local console.
    Optionally, you can specify a fallback account which will be used for replacing accounts in backup schedule tasks if these accounts cannot be replicated to the local console. It is recommended to specify a fallback account if backup schedule tasks use a regular Active Directory account, a local account or a gMSA account that cannot be resolved on the local console. Otherwise, the replication will fail.
  5. Supply the credentials for the replication task. These credentials will be used to connect the source console that you have just added.

    NOTE:

    • The account used for the replication task must be a member of the local Administrators group on the local and remote RMAD consoles.
    • The account must be a member of the Domain Users group on each target domain.
    • The account must be a member of the local Administrators group on the computer hosting the AD LDS (ADAM) instances.
  6. Now the source console instance is added and shown in the right pane.
  7. Set the console replication status to Enabled in the right pane.
  8. To start the replication, right-click Remote Consoles and press Replicate.
  9. To change the console properties, right-click the console instance from the list in the right pane and select Properties.
  10. To remove the console instance from the replication console list, right-click the instance and click Remove.

IMPORTANT: To activate the slave console in case of the master console failure, go to the Remote Consoles node and set the replication status of the master console to Disabled in the right pane. This action turns off the read-only mode on the slave console and the console completely takes over the functions of the master one.

Replication status

  • If the data replication is finished successfully, the status in the console instances list is changed to "Success".
  • The replication may fail with the error "Cannot connect to Recovery Manager for Active Directory on the specified computer." in the following cases:
    • If the target computer does not exist or Recovery Manager for Active Directory is not installed on the specified host.
    • If the Recovery Manager Remote API Access service is not installed or stopped
    • If you experience network connection problems
    • If the account that is used for the replication task is blocked, etc.

To view the replication history

  1. Open the local Recovery Manager for Active Directory console.
  2. Click History under the Replication node to view the list of replication sessions.
  3. If you click a replication session, the right pane shows all remote consoles that are involved in the specified replication session.
  4. To remove one or more replication sessions from the list, right-click the session node and select Delete. Multi-select is possible.

To create a replication schedule

  1. In the Recovery Manager for Active Directory console, right-click the Replication node and select Properties.
  2. In the Replication Properties dialog, you can create the replication schedule. For that, click Modify..., then click New... in the Recovery Manager Replication Job dialog to create a trigger for the schedule.
  3. Make sure that the Schedule enabled option is selected in the Replication Properties dialog.
  4. Provide a user account that will be used to start the replication schedule task using Select Account... in the Replication Properties dialog. Minimum requirements for the account are listed above depending on the replication mode.
  5. Click OK.

Note: You can specify Managed Service Account (in Windows Server 2008 or higher) or Group Managed Service Account (in Windows Server 2012 or higher) to run the replication schedule task. Note that you must add the '$' character at the end of the account name (e.g. domain\computername$) and leave the Password field blank. This account must be a member of the local Administrator group on the Recovery Manager for Active Directory machine.

Related Documents