Chat now with support
Chat mit Support

Recovery Manager for AD Disaster Recovery Edition 10.1.1 - 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 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-RMADFEComputer Add-RMADReplicationConsole Add-RMADStorageServer Backup-RMADCollection Close-RMADFEProject Compare-RMADObject Convert-RMADBackup ConvertTo-RMADRecycledObject Create-RMADStorageManagementAgentSetup Expand-RMADBackup Export-RMADBackup Export-RMADFERecoveryCertificate Export-RMADFEResult Get-RMADBackup Get-RMADBackupAgent Get-RMADBackupInfo Get-RMADBackupObject Get-RMADBackupSecurityStatus Get-RMADCollection Get-RMADCollectionItem Get-RMADDeletedObject 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-RMADStorageServers Import-RMADBackup Import-RMADFERecoveryCertificate Install-RMADBackupAgent Install-RMADFERecoveryAgent New-RMADCollection New-RMADFEProject New-RMADFERecoveryMedia New-RMADSchedule Open-RMADFEProject Publish-RMADBackupSecurityStatus Remove-RMADBackup Remove-RMADBackupAgent Remove-RMADCollection Remove-RMADCollectionItem Remove-RMADFEComputer 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 Start-RMADFERecovery Start-RMADFEVerification Start-RMADReplication Start-RMADReportViewer Stop-RMADFEWorkflow Update-RMADBackupAgent Update-RMADFEProject Update-RMADLicense

Backing up cross-domain group membership

When backing up Active Directory on a Global Catalog server, Recovery Manager for Active Directory enables the backup to include the object’s membership in all groups, including those groups that reside in domains outside the object’s home domain.

This option is part of the backup creation settings. You can find it on the Advanced tab in the Properties dialog box for a Computer Collection. The option only takes effect when backing up Global Catalog servers.

If this option is not selected, group membership spanning multiple domains is not fully backed up, because even Global Catalog servers do not store full information about group memberships. For example, information about membership in domain local groups is only stored in the home domains of those groups.

To ensure that cross-domain group membership information is backed up
  1. Do one of the following:

    • When creating backups for a Computer Collection, right-click the Computer Collection, and then click Properties.

    • When creating backups using the Backup Wizard, click the Advanced button on the Completing the Backup Wizard page of the wizard.

  2. In the Properties dialog box, click the Advanced tab.

  3. On the Advanced tab, make sure the When backing up Global Catalog servers, collect group membership information from all domains within the Active Directory forest check box is selected.

Using a Global Catalog backup created with this option ensures the complete restoration of object group memberships in all domains within the forest.

However, this option causes Recovery Manager for Active Directory to retrieve data from all domains within the forest, and therefore may slow down the backup creation in case of a big number of domains or slow network connections.


Backing up distributed file system (DFS) data

When backing up a domain controller, Recovery Manager for Active Directory can also back up the domain-based Distributed File System (DFS) namespace data located on the domain controller. DFS namespace data is backed up as part of SYSVOL. You can use the created backup to recover the domain-based DFS namespace.

Note that Recovery Manager for Active Directory cannot back up the DFS namespace links to the actual folders and files, as well as these folders and files. Also Recovery Manager for Active Directory does not support standalone DFS namespace data.


Backup scheduling

In Recovery Manager for Active Directory, a backup for a computer or a collection of computers can be created manually, or the creation of backups can be scheduled to occur at a specific time in the future. Backups can be stored in any appropriate location on your network.


Task scheduler overview

When scheduling backup creation, Recovery Manager for Active Directory employs Task Scheduler, which is an integral part of the operating system. You can access the Task Scheduler GUI by clicking Scheduled Tasks in Control Panel. The Scheduled Tasks dialog box displays all tasks scheduled to run on your computer.

Each scheduled task runs under a certain user account. Therefore, you must supply the user logon name and password of a user account when creating a scheduled task. When performing the scheduled backup job, Recovery Manager for Active Directory runs as if that user started it.

The user account under which Recovery Manager for Active Directory is running when creating backups must

  • Belong to the Administrators local group on the Recovery Manager for Active Directory computer.

  • Belong to the Administrators local group on each computer to be backed up (serviced computer).

When scheduling a backup job, you should ensure that the account whose credentials you are supplying meets the above requirements. If there are no trust relationships established between the domains where the Recovery Manager for Active Directory computer and the serviced computer reside, then no account can satisfy both of the above requirements. To resolve this problem, you can specify a different account to access the serviced computer.

In the “no trust” situation, when scheduling a backup job, you should use an account that meets the first of the above requirements, and configure advanced backup options so that a different account is used for access to the serviced computers, satisfying the second requirement.


Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen