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

Disaster recovery workflow

This following steps let you restore multiple domain controllers including the Active Directory® data if a disaster occurs.

  1. Deploy Recovery Manager for Active Directory.

    The product should be deployed on a separate host in the environment with access to backup data and blank hosts that will be a part of the disaster forest recovery.

  2. Register backups in Recovery Manager for Active Directory Console. For that, right click the Backups node and select Register Backup File option. Also, backups can be registered using Forest Recovery Console on the Selected a backup to create a new recovery project step of the New Recovery Project wizard.

  3. Prepare new servers for recovered domain controllers in each domain. These servers will be used for Bare Metal Restore. The servers should be compliant with the following requirements:

    • Have compatible hardware. Dissimilar hardware (USB controllers, chipset, NIC, video, storage, etc.) is supported, assuming that the source DC system contains drivers for it.

    • The number of physical disks on the target computer must equal (or exceed) the number of disks on the source domain controller.

    • The physical disks on the target computer must be of the same size as the original disks or larger.

  4. Create the forest recovery project using Forest Recovery Console. The original forest topology is retrieved from the backup file. Domain controllers’ names are preserved.

    Resources/Images/WindowsBackup-02.png

  5. Specify recovery settings for each domain controller on the General tab in Forest Recovery Console. For more details, see the General tab section.

  6. If Wipe all disks on the target machine before restore from the backup is selected on the General tab, Recovery Manager for Active Directory performs the DiskPart "clean all" command before recreating the disks. This command removes all partitions and cleans all disk sectors.

  7. The network and DNS settings address will be retrieved automatically from the BMR backup for the Bare Metal Active Directory® Recovery method.

    Resources/Images/SecondStage2.png

    Resources/Images/NetworkSettings_FR.png

  8. If you need to modify the network settings, click Change under the Target server network settings and select the required option. The following options are available:

    • Retrieve network and DNS settings from a backup - (used by default) This option gets network settings for the selected domain controller from the backup

    • Use the following address - This option lets you specify network settings manually.

    • Select a DNS server automatically - If this option is selected, DNS server will be selected automatically.

    • Use the specified DNS server - This option lets you specify one DNS server or a list of DNS servers separated by semicolons.

    Resources/Images/NetworkSettingsFR.png

  9. In some scenarios, recovered domain controllers may be located outside the network where Recovery Manager for Active Directory is installed. For such configurations, the NAT settings option is added to allow access to the external network using the NAT server. By default, Forest Recovery Console uses the IP address from the Forest recovery project settings (either obtained from a backup or configured manually, see steps 7 and 8) and the port (either from the RPC dynamic port range or the specific port configured in the recovery project) to communicate with the Forest Recovery Agent located on the restored host. The 'NAT server' setting allows you to specify a custom IP address and a port that will be used to send requests to the Forest Recovery Agent.

    Resources/Images/rmad-nat.png

  10. Start the Verify Settings operation from the main menu of Forest Recovery Console.

  11. As a part of the verify settings operation, Recovery Manager for Active Directory creates Quest Recovery Environment image file for each domain controller. This image file will be used to boot the machine to be restored. The image is generated from BMR backup and extends the WinRE image with additional metadata required for disaster forest recovery (Forest Recovery Agent, Bare Metal Recovery Console, certificates, etc).

    NOTE: Find the extracted Windows imaging file WimRe.wim under \ProgramData\Cache\WinRe\10.0 folder on the RMAD machine. Cache and reuse the extracted WinRe images for BMR, which will reduce failures while creating ISO images from backup.

  12. The Verify Settings process is paused on the Wait for target machine booted from Quest Recovery Environment step. This means that the recovery process cannot connect the remote host and you need boot this host with Quest® Recovery Environment image. The message contains the link to the folder with Quest Recovery Environment files (by default, the files are located next to the BMR backup).

  13. The recovery image should be provided to the target hosts to initiate the recovery process by any available option:

    • By the hardware management WebUI

    • By specifying the boot media in hypervisor if virtual machines are used

    • By configuring the network boot using the PXE boot server

    • The booting process can be automated by a server controller, e.g Dell™ Remote Access Controller (iDRAC), HP® ProLiant iLO Management Engine (iLO), etc. For details, see Boot from the ISO image automatically

  14. After you boot a machine, Bare Metal Recovery Console will automatically apply network settings (IP address, subnet mask) taken from the BMR backup and wait for the connection from Forest Recovery Console. Manual steps are not required.

  15. Before you start the restore operation, check the boot order for the remote machine. Ensure that the target machine is trying to boot from the disk drive not from Quest Recovery Environment.

    Resources/Images/EjectRecoveryImage.png

  16. Start the restore operation by clicking Start Recovery from the main menu.

"Install Active Directory" recovery method can be used as a part of the Disaster Recovery workflow.

 

Boot from the ISO image automatically

The process of booting the physical server with Quest Recovery Environment image can be automated by a management engine. Recovery Manager for Active Directory supports the following server management systems:

 

Dell Remote Access Controller (iDRAC)

The process of booting of Dell™ server with Quest Recovery Environment image can be automated by Dell™ Remote Access Controller (iDRAC).

Supported versions

Integrated Dell™ Remote Access Controller version 8 and 9

To boot the Dell™ server with Quest Recovery Environment image automatically

  1. In Forest Recovery Console, open the Infrastructure tab.

    Resources/Images/Host_controller_Dell.png

  2. Select Dell server from the Infrastructure drop-down list.

  3. Specify the IP address of the iDRAC controller. It is recommended to specify the IP address of the controller instead of the server name.

    NOTE: For Dell™ server, Quest Recovery Environment ISO image should be located in the share root folder.

  4. Specify the user name and password of the account that will be used to access the iDRAC controller.

  5. You can edit the iDRAC SSH script manually in the following location: %ProgramFiles%\Quest\Recovery Manager for Active Directory <Edition Name>\Management. This script will be run on the remote server during the SSH session.

  6. Make sure that Recovery Media Image settings are properly specified in the Recovery Media Image section of the Infrastructure tab.

 

HPE ProLiant iLO Management Engine (iLO)

The process of booting the HPE® server with Quest Recovery Environment image can be automated by HPE® ProLiant® iLO Management Engine (iLO).

Supported versions

HPE® ProLiant® iLO Management Engine version 3, 4 and 5

To boot the HPE server with Quest Recovery Environment image automatically

  1. Install the latest version of HPEiLOCmdlets. For details, see HPE Support.

  2. In Forest Recovery Console, open the Infrastructure tab.

  3. Select HP server from the Infrastructure drop-down list.

    Resources/Images/Host_controller_HP.png

  4. Specify the IP address of the iLO controller.

  5. Specify the user name and password of the account that will be used to access the iLO controller.

  6. You can edit the iLO PowerShell® script manually in the following location: %ProgramFiles%\Quest\Recovery Manager for Active Directory <EditionName>\
    Management\iLO.ps1

  7. Make sure that Recovery Media Image settings are properly specified in the Recovery Media Image section of the Infrastructure tab.

  8. You can change the default port (8080) used by the web server handling the HPE® iLO requests for the Quest Recovery Media Images by modifying the RecoveryMediaHttpServicePort value in the FRConsoleSettings.xml file. For more information on configuring advanced settings for the Forest Recovery Console in the FRConsoleSettings.xml file, see Configuring advanced settings.

  9. Make sure the firewall rules on the Forest Recovery Console allow inbound connections to the Quest Recovery Media Images web server from iLO server.

 

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation