These release notes provide information about the Quest® Recovery Manager for Active Directory release.
Recovery Manager for Active Directory enables fast, online recovery. Comparison reports highlight what objects an attributes have been changed and deleted in Active Directory enabling efficient, focused recovery at the object or attribute level. Accurate backups and a quicker recovery enable you to reduce the time and costs associated with AD outages and reduce the impact on users throughout your organization.
Recovery Manager for Active Directory is based on patented technology.
Recovery Manager for Active Directory 10.0.1 is a maintenance release with new features and functionality. See New features.
New features and enhancements in Recovery Manager for Active Directory 10.0.1:
|Support for Microsoft Windows Server 2019 |
This release can be installed on computers running Windows Server 2019, and domain controllers running Windows Server 2019 can be targets for backup and restore operations.
|Continuous recovery (Change Auditor integration) |
Recovery Manager for Active Directory restores a deleted object and the last change (if any) that was made to the object properties after the backup creation using data from the Change Auditor database.
|Support for restore of Group Policy Objects in non-trusted domains |
Domain access credentials can be explicitly specified in Group Policy Restore Wizard.
|Support for Azure Files as a backup storage |
Recovery Manager for Active Directory can work with backups stored in the Azure Files share.
|Separate accounts to access the backup storage and the Backup agent |
Now a user can access backup storage share under specified account, which is not the same as an account used to access the backup agent.
Table 1: General resolved issues
|Resolved Issue||Issue ID|
|Now Backup Agent retries to connect to the LDAP server if it is not functional during start of the backup creation process.||RMADFE-1954|
|RMAD console may hang during startup on Windows Server 2016 with some updates.||RMADFE-2006|
|Now log information about backup creation sessions is written to the text file specified on the Alerts tab of the collection properties.||RMADFE-2025|
|Recovery Manager Console could show misleading "agent is up to date" message when the version of Backup agent did not match the console version.||RMADFE-2054|
|Recovery Manager for Active Directory can open a DIT database as Read/Write from backups made on other versions of operating system.||RMADFE-2091|
|Now we show the warning during the backup session if the agent is not up to date.||RMADFE-2096|
|Now Recovery Manager Console starts with no MMC errors.||RMADFE-2097|
|Now the error is shown if an AD component is copied incompletely from the VSS snapshot.||RMADFE-2127|
|MSA/gMSA accounts now can be used for scheduled backups on localized Windows operating systems.||RMADFE-2145|
|Support for RMAD backup and restore operations for Windows Server 2019 domain controllers.||RMADFE-2168|
|Unable to uncheck two options on the Components tab of the collection properties: "When backing up Global Catalog servers, collect group membership information from all domains within the Active directory forest" and "Collect Forest recovery metadata".||RMADFE-2183|
|Support for RMAD backup and restore operations for Windows Server 2019 Core domain controllers.||RMADFE-2211|
|In some cases, a license violation warning may appear in Recovery Manager Console.||RMADFE-2249|
|Unable to change access credentials during the Agent-less Online Restore when the "Require trusted path for credential entry" policy is enabled.||RMADFE-2259|
|Unable to change access credentials during the Agent-based Online Restore when the "Require trusted path for credential entry" policy is enabled.||RMADFE-2306|
|Now 'Boot Files' and 'IIS Metabase' backup components are hided.||RMADFE-2343|
|Recovery Manager cannot process large .dit files.||RMADFE-2349|
|When specifying the port for the Offline Restore Agent on the Ports tab of the Recovery Manager Console Settings, Recovery Manager for Active Directory still connects via a random port.||RMADFE-2289|
|Recovery Manager for Active Directory does not restore some attributes in the hybrid configuration because of incorrect attribute matching.||RMADFE-2499|
|The Online Restore Wizard did not accept long paths to the Change Auditor database.||RMADFE-2567|
|Recovery Manager cannot backup a DC if SYSVOL is placed on a deduplicated volume.||RMADFE-2582|
The following is a list of issues, including those attributed to third-party products, known to exist at the time of release.
Table 2: Recovery Manager for Active Directory known issues
|Known Issue||Issue ID|
|Online Restore Wizard (agent-based restore) does not work on Windows Server 2019 with Local Security Authority (LSA) protection enabled.||RMADFE-2182|
|Online Restore Wizard (agent-based restore) does not work on Windows Server 2016 with Local Security Authority (LSA) protection and Secure Boot enabled.||RMADFE-1996|
|Cannot perform RMAD upgrade if the SQL Server Always On group is enabled for the reporting database.||RMADFE-1146|
You may encounter the following unexpected behavior on the Backup Data Preparation step of the Online Restore Wizard: The wizard may not respond to any user action while it is processing a backup.
WORKAROUND: Wait until the backup processing is finished.
When you select the "Backup Agent Management" node in the Recovery Manager Console, you may observe the following issue: The Recovery Manager Console stops responding, showing the status "Discovering Backup Agent instances, please wait".
WORKAROUND: Wait until the Backup Agent discovery completes.
Unexpected behavior on the Reporting Options step in the Online Restore Wizard: When you select the "Include ChangeAuditor data in reports" check box, select a ChangeAuditor database, and click Next, you may encounter the error "Unable to connect to the ChangeAuditor database: <database>. Details: Login failed for user '<current user>'."
This error shows up if the current user account does not have sufficient permissions to access the ChangeAuditor database. The expected behavior in the described situation is that the Online Restore Wizard should prompt you for credentials to access the ChangeAuditor database.
WORKAROUND: Run the Online Restore Wizard under an account that has sufficient permissions to access the target ChangeAuditor database.
You may encounter the following unexpected behavior while using the "Backup Agent Management" view in the Recovery Manager Console to view a list of Backup Agents: The list of Backup Agents may be incomplete. The cause of this behavior is that when you apply a filter on one or more columns in the "Backup Agent Management" view, there is no indication that the filter is applied.
WORKAROUND: Check to see if a filter is applied on any columns in the "Backup Agent Management" view. Remove the filter if necessary.
A compare operation performed in the Online Restore Wizard may take a significant time to complete (30+ minutes). Also, the compare operation may consume a significant amount of RAM. This issue only occurs if the number of objects being compared is 100,000+.
WORKAROUND: Wait for the compare operation to complete.
The Online Restore Wizard cannot find an object if the object name contains 1-9 digits when searching by the full object name, but can find it by the common mask, for example: 'u01' object can be found by 'u' and cannot by 'u01'.
This issue may arise if the operating system version of a domain controller is greater or different from the RMAD Console machine operating system.
WORKAROUND: Copy the esent.dll file from the domain controller where the backup was created to the product installation folder on the Recovery Manager Console machine.
You may receive the "ASR Error: Fail to exclude disk#1" error when performing the Backup or Restore operation on Windows Server 2008/2008R2-based domain controller.
WORKAROUND: This error can be safely ignored because it does not affect the backup or restore process.
After the upgrade on the network isolated machine, the Recovery Manager Console is loaded too slowly.
WORKAROUND: Uncheck the Check for publisher's certificate revocation option on the Advanced tab in the Internet Option dialog in Microsoft Internet Explorer.
Pre-installed Backup Agent can be upgraded during the backup creation.
WORKAROUND: Do not upgrade Backup Agent if the backup operation is not finished.
|When a user cancels the data replication process by Ctrl + C, by logoff, etc, the status of the replication session is stuck at "Running".||RMADFE-1271|
|Customer can add a few instances of the same RMAD console (by domain name and by IP).||RMADFE-1276|
Cannot disable replication schedule when there is no replication console (the replication console was deleted).
Group Policy restore might fail with the error "Network access is denied” if you run the RMAD console under a local account, and this account has the same username and password as the domain account you use to restore Group Policy in the domain.
Table 3: Recovery Manager Portal known issues
|Known Issue||Issue ID|
Unexpected behavior when you use the Recovery Manager Portal to delegate restore or undelete permissions to a user or group that is not assigned any role in the Recovery Manager Portal: The delegation operation completes successfully. The expected behavior in this situation is that the Recovery Manager Portal should not allow you to delegate permissions to a user or group that has not been assigned any role in the portal.
WORKAROUND: Before delegating restore or undelete permissions, ensure that the target user or group is assigned the appropriate role in the Recovery Manager Portal. For more information about assigning roles to portal users, see the "Using Recovery Manager Portal" chapter in the User Guide.
The Recovery Manager Portal fails to show the result of a restore or undelete operation if while the restore or undelete is still running you switch to some other tab, and then return to the Recovery tab.
To ensure that all objects have been successfully restored or undeleted:
When selecting a backup the Recovery Manager Portal, you may encounter the error "No backup found for the last backup session." This issue occurs if the backup is located on the domain controller and in the Recovery Manager Console its storage location is specified using a UNC path.
WORKAROUND: Select a backup stored locally on the Recovery Manager for Active Directory computer.
Cannot access the Recovery Manager Portal if the portal is installed in the child domain.
WORKAROUND: In the portal settings file C:\Program Files (x86)\Quest\Recovery Manager Portal\Enterprise.Portal.Console\bin\EnterprisePortalSettings.xml <add key="SimulateLogonForWebDelegation" value="false" /> (default = true)