지금 지원 담당자와 채팅
지원 담당자와 채팅

Recovery Manager for AD Disaster Recovery Edition 10.2 - 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 Secure Storage servers 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 Bare metal forest recovery Using Management Shell Creating virtual test environments Using Recovery Manager for Active Directory web portal 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 Descriptions of PowerShell commands
Add-RMADBackup Add-RMADCollectionItem Add-RMADReplicationConsole Add-RMADStorageServer Backup-RMADCollection Close-RMADFEProject Compare-RMADObject Convert-RMADBackup ConvertTo-RMADRecycledObject Copy-RMADFEBackup Create-RMADStorageAgentSetup Expand-RMADBackup Export-RMADBackup Export-RMADFERecoveryCertificate Export-RMADFEResult Export-RMADSecureStorageBackup Get-RMADBackup Get-RMADBackupAgent Get-RMADBackupInfo Get-RMADBackupObject Get-RMADBackupSecurityStatus Get-RMADCollection Get-RMADCollectionItem Get-RMADDeletedObject Get-RMADFEAvailableSubnet Get-RMADFEComputer Get-RMADFEConsole Get-RMADFEDnsCache Get-RMADFEDomain Get-RMADFEEvent Get-RMADFEGlobalOptions Get-RMADFEOperation Get-RMADFEPersistenceConnection Get-RMADFEProject Get-RMADFERecoveryAgent Get-RMADFESchedule Get-RMADGlobalOptions Get-RMADLicenseInfo Get-RMADObject Get-RMADReplicationConsole Get-RMADReplicationSchedule Get-RMADReplicationSession Get-RMADReplicationSessionItem Get-RMADReportObject Get-RMADReportObjectAttributes Get-RMADReportObjectChildren Get-RMADReportSession Get-RMADSession Get-RMADSessionItem Get-RMADSessionItemEvent Get-RMADStorageServer Get-RMADStorageServerHardeningStatus Get-RMADStorageServerRetentionPolicy Import-RMADBackup Import-RMADFERecoveryCertificate Install-RMADBackupAgent Install-RMADFERecoveryAgent New-RMADCollection New-RMADFEProject New-RMADFERecoveryMedia New-RMADSchedule Open-RMADFEProject Protect-RMADSecureStorageServer Protect-RMADStorageServer Publish-RMADBackupSecurityStatus Refresh-RMADStorageServer Register-RMADSecureStorageBackups Remove-RMADBackup Remove-RMADBackupAgent Remove-RMADCollection Remove-RMADCollectionItem Remove-RMADFERecoveryAgent Remove-RMADFESchedule Remove-RMADReplicationConsole Remove-RMADReplicationSchedule Remove-RMADReplicationSession Remove-RMADStorageServer Remove-RMADUnpackedComponent Rename-RMADCollection Restore-RMADDeletedObject Restore-RMADDomainController Restore-RMADObject Resume-RMADFERecovery Save-RMADFEProject Set-RMADCollection Set-RMADFEComputer Set-RMADFEDnsCache Set-RMADFEDomain Set-RMADFEGlobalOptions Set-RMADFEPersistenceConnection Set-RMADFERecoveryMode Set-RMADFESchedule Set-RMADGlobalOptions Set-RMADReplicationConsole Set-RMADReplicationSchedule Set-RMADStorageServerRetentionPolicy Start-RMADFERecovery Start-RMADFERecoveryAgentOperation Start-RMADFEVerification Start-RMADReplication Start-RMADReportViewer Stop-RMADFEWorkflow Test-RMADSecureStorageBackup Unprotect-RMADStorageServer Update-RMADBackupAgent Update-RMADFEProject Update-RMADLicense

HP ProLiant iLO Management Engine (iLO)

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

Supported versions

HP ProLiant iLO Management Engine version 3, 4 and 5

To boot the HP server with Quest Recovery Environment image automatically

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

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

  3. Select PhysicalHP from the Infrastructure drop-down list.

Resources/Images/Host_controller_HP.png

  1. Specify the IP address of the iLO controller.

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

  3. You can edit the iLO PowerShell script manually in the following location: %ProgramFiles%\Quest\Recovery Manager for Active Directory <Edition Name>\Management.

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

  5. You can change the port used by the web server handling the HP 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.

 

VMware ESXi

The process of booting the VMware virtual machine with the Quest Recovery Environment image can be automated by VMware ESXi.

NOTE

This feature allows you to work directly with ESXi hosts and VMware Center.

Supported versions

VMware vCenter/ESX Server 6.0, 6.5, 6.7 and 7.0

Prerequisites

VMware PowerCLI PowerShell module must be installed.

Minimal Rights and Permissions

Privilege Name Actions Granted to Users Effective on Object Propagate to Children
System.View Allows a user to get information about vCenter/ESXi configuration in user interface. vCenter Yes
Datastore.FileManagement Allows a user to carry out file operations in the datastore browser. Datacenter, Datastore storage folder, Datastore Cluster, Datastore Yes
Datastore.Browse Allows browsing files on a datastore, including CD-ROM or Floppy media and serial or parallel port files. In addition, the browse datastore privilege allows users to add existing disks to a datastore. Datacenter, Datastore storage folder, Datastore Cluster, Datastore Yes
Datastore.AllocateSpace Allows allocating space on a datastore for a virtual machine, snapshot, clone, or virtual disk. Datacenter, Datastore storage folder, Datastore Cluster, Datastore Yes
VirtualMachine.Inventory.Create Allows creating a new virtual machine and allocates resources for its execution. Datacenter, Virtual machine folder Yes
VirtualMachine.Config.AddNewDisk Allows creation of a new virtual disk to add to a virtual machine. Datacenter, Virtual machine folder Yes
VirtualMachine.Interact.SetCDMedia Allows configuration of a virtual DVD or CD-ROM device. Datacenter, Virtual machine folder, Cluster, Host Yes
VirtualMachine.Interact.DeviceConnection Allows changing the connected state of a virtual machine’s disconnectable virtual devices. Datacenter, Virtual machine folder, Cluster, Host Yes
VirtualMachine.Config.Settings Allows changing any basic settings such as those in ToolsConfigInfo, FlagInfo, or DefaultPowerOpInfo Datacenter, Virtual machine folder, Cluster, Host Yes
VirtualMachine.Interact.PowerOff Allows powering off a powered-on virtual machine. Datacenter, Virtual machine folder, Cluster, Host Yes
VirtualMachine.Interact.PowerOn Allows powering on a powered-off virtual machine, and resuming a suspended virtual machine. Datacenter, Virtual machine folder, Cluster, Host Yes
Resource.AssignVMToPool Assigns a virtual machine to a resource pool. Datacenter, Cluster, Host Yes
Network.Assign Assigns a virtual machine to a network. Datacenter, Network folder, Network Yes

Precautions (only for test environments)

  • Virtual test environments created with this option can only be used for testing, training, or evaluation purposes. Never restore or copy any data from your virtual test environments to the production Active Directory.

  • Ensure your virtual test environment is properly isolated from the source Active Directory forest. Otherwise, the source forest may be seriously damaged after you enable the network adapters in the newly-created virtual test environment.

To boot the VMware virtual machine with the Quest Recovery Environment image automatically

  1. In Forest Recovery Console, select the DC that you want to recover and open the Infrastructure tab.

  2. Select VMWare ESXi from the Infrastructure drop-down list.

Resources/Images/VM_ware2_v2.png

  1. To configure default settings, click View. For more information see, Specifying recovery project settings.

Resources/Images/VM_ware2_2.png

  1. Specify the connection settings for the vSphere Web Client.

  2. Specify the user name and password of the account that will be used to access vSphere Web Client.

  3. Use the Name text box to type a name for the virtual machine on the target computer. The machine with this name will be used if Create virtual machine is unchecked, or will be created if the option is selected.

  4. You can create a new virtual machine based on the configuration from backup and specified settings. For that, select the Create virtual machine option. The following settings can be specified:

    • Host name - Specify the ESXi host where you want to place the virtual machine. Multi-select can be used to select several DCs.

    • Refresh - Refreshes the information.

    • VM folder - Select the folder in which you want to place the target virtual machine. Nested folders are supported.

    • Network - Specify the virtual network.

    • Storage - Select the storage in which to place the virtual machine files.

    • Space available - Shows free space in the storage.

    • Number of processors - Specify the number of processors you want to have on the target virtual machine.

    • Memory size - Set the amount of random access memory you want to allocate to the target virtual machine.

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

 

Microsoft Hyper-V

The process of booting the virtual machine with the Quest Recovery Environment image can be automated by Microsoft Hyper-V.

Supported versions

Hyper-V Server 2012 or higher

NOTE

Recovery Manager for Active Directory does not directly support System Center Virtual Machine Manager (SCVMM) for this feature but you can work with SCVMM-managed Hyper-V hosts.

Precautions (only for test environments)

  • Virtual test environments created with this option can only be used for testing, training, or evaluation purposes. Never restore or copy any data from your virtual test environments to the production Active Directory.

  • Ensure your virtual test environment is properly isolated from the source Active Directory forest. Otherwise, the source forest may be seriously damaged after you enable the network adapters in the newly-created virtual test environment.

To boot the virtual machine with the Quest Recovery Environment image automatically

  1. In Forest Recovery Console, select the DC that you want to recover and open the Infrastructure tab.

  2. Select Microsoft HyperV from the Infrastructure drop-down list.

Resources/Images/Hyper_V_v2.png

  1. To configure default settings, click View. For more information see, Specifying recovery project settings.

Resources/Images/Hyper_V_2.png

  1. Specify the connection settings for the Hyper-V host.

  2. Specify the user name and password of the account that will be used to access the Hyper-V host. This account must have the following permissions:

    • Be a member of the local Administrators group on the target Hyper-V host

    • Be able to access admin$ share on the target Hyper-V host

    • Be a member of the Hyper-V Administrators group

    Recovery Manager for Active Directory uses PowerShell Remoting to manage the HyperV server. The required permissions must be configured for users that are used to access the Hyper-V host, especially when the host is outside the domain where the Forest Recovery Console is running. For details, see https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts.

  3. Use the Name text box to type a name for the virtual machine on the target computer. The machine with this name will be used if Create virtual machine is unchecked, or will be created if the option is selected.

  4. You can create a new virtual machine based on the configuration from backup (generation of Hyper-V virtual machine, number of disks, disk sizes) and specified settings. For that, select the Create virtual machine option. The following settings can be specified:

    • Network - Specify the virtual network.

    • Storage - Select the storage in which to place the virtual machine files on the Hyper-V host.

    • Space available - Shows free space in the storage.

    • Number of processors - Specify the number of processors you want to have on the target virtual machine.

    • Memory size - Set the amount of random access memory you want to allocate to the target virtual machine.

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

 

Custom host controllers

The process of booting the custom server with the Quest Recovery Environment image can be automated by a custom management system.

To boot the custom server with Quest Recovery Environment image automatically
  1. In Forest Recovery Console, open the Infrastructure tab.

Resources/Images/custom_host_controller.png

  1. Select Custom from the Infrastructure drop-down list.

  2. Specify the IP address of the custom controller.

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

  4. Configure and specify the Eject script and the Boot script for the ISO image.

  5. To edit the custom SSH script or PowerShell script manually, go to the following location: %ProgramFiles%\Quest\Recovery Manager for Active Directory <Edition Name>\Management. The SSH 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.

 

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택