Recovery Manager for AD 10.2 - User Guide

Removing a Backup Agent entry from the Backup Agent Management node

You can selectively remove Backup Agent entries from the list provided in the Backup Agent Management node. Removing a Backup Agent entry from that list does not affect the corresponding preinstalled agent instance in any way. Rather, it removes the agent’s registration information from the Recovery Manager Console.

You may want remove a Backup Agent entry from the list when, for example, you have uninstalled the corresponding Backup Agent instance from the computer without using the Recovery Manager Console, and the agent entry remained in the Backup Agent Management node.

To remove a Backup Agent entry

1. In the Recovery Manager Console tree, select the Backup Agent Management node.

2. In the right pane, right-click the Backup Agent entry you want to remove from the list.

3. From the shortcut menu, select Remove from List.

Using a least-privileged user account to back up data

You can configure Recovery Manager for Active Directory to back up data in an Active Directory domain under a least-privileged user account. A least-privileged user account is an account that has no other permissions except for those required to back up data with Recovery Manager for Active Directory.

Using a least-privileged account to back up Active Directory offers greater protection from unwanted changes to your Active Directory environment, security attacks, or unsolicited access to sensitive documents or settings.

To run backup operations under a least-privileged user account, in the domain you want to back up, create an Active Directory group named RMAD Backup Operators. Add the least-privileged user account you want to that group, and then preinstall the Backup Agent in the domain. As a result, members of the RMAD Backup Operators group are automatically granted the necessary permissions to back up data in the domain with Recovery Manager for Active Directory.

To use a least-privileged user account for backup operations

1. In the Active Directory domain you want to back up, create a new Active Directory group with the following name: RMAD Backup Operators

2. To the RMAD Backup Operators group, add the least-privileged user account under which you want to back up the domain.

3. On the domain controllers you want to back up, preinstall the Backup Agent version supplied with this release of Recovery Manager for Active Directory.

   Make sure you first create the RMAD Backup Operators group, and then install the Backup Agent in the domain. During its installation, the agent locates that group and saves the group SID in the registry. Then the Backup Agent uses this group SID to check that the user account is a member of the RMAD Backup Operators group.

   If the Backup Agent supplied with this release is already preinstalled, you can repair the agent’s installation so that the agent could locate the RMAD Backup Operators group.

4. Add the domain controllers on which you preinstalled the Backup Agent to a new Computer Collection.

5. In the Computer Collection properties, on the Agent Settings tab, do the following:

   • Specify to access the Backup Agent with the least-privileged account you have added to the RMAD Backup Operators group.

   • Select the check box to use preinstalled Backup Agent. For more information, see Agent Settings tab subsection in Properties for an existing Computer Collection.

6. Back up the Computer Collection.

Using Managed Service Accounts

Recovery Manager for Active Directory supports MSA/gMSA accounts for:

• Scheduled backups - the account can be specified for scheduled tasks in the Computer Collection properties on the Schedule tab or in Task Scheduler.

• Scheduled replication tasks (Fault Tolerance)

• The Recovery Manager Portal can be run under the MSA/gMSA account. During the Recovery Manager Portal installation, specify the MSA/gMSA on the Specify Web Site Settings step of the wizard.

MSA/gMSA account requirements:

• You can use Managed Service Account (in Windows Server 2008 or higher) or Group Managed Service Account (in Windows Server 2012 or higher).

• Add the $ character at the end of the account name (e.g. domain\computername$) and leave the Password field blank.

• The MSA/gMSA account must be a member of the local Administrator group on the Recovery Manager for Active Directory machine.

• For more details about account requirements and limitations related to Recovery Manager Portal, see the Install or uninstall Recovery Manager Portal section in Permissions required to use Recovery Manager for Active Directory.

How to create a Group Managed Service Accounts (gMSA)

1. Create a gMSA account in Active Directory using the following command: New-ADServiceAccount -name @<gMSA account name> -DNSHostName @<DNS host name>

2. Run Install-AdServiceAccount @<gMSA account name> on each host where you are going to use this gMSA account.

What are the steps to configure a gMSA account for use as the backup agent account using the minimum permissions model?

1. Create а gMSA and associate its principal with the computer accounts of the member hosts. If you want to manage the service host permission to use a gMSA account by a security group, you can associate the account principal with a security group. And then assign the Recovery Manager for Active Directory server(s) machine accounts as members of the linked security group.

2. Create the Active Directory group RMAD Backup Operators and add the gMSA account to this group directly.

3. If using pre-installed agents, uninstall and reinstall the agents. This is required to populate the RMAD Backup Operators group SID locally on the DCs.

4. Configure the collection properties to set the backup agent access account. When entering the gMSA credentials, input the username as "domain\gMSA$", where gMSA is the service account login name followed by the $ sign, and leave the password fields blank.

Take consideration that some items are not possible to configure when using the minimum permissions group, such as "Ensure Forest Recovery Agent is deployed".
This setting requires that you have DC Administrator access, and access to the admin$ share.
If you want to have this set up, the gMSA will need to be a member of Domain Admins, instead of RMAD Backup Operators.

For more details, see https://docs.microsoft.com/en-us/windows-server/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts.

Active Directory backups vs Windows System State backups

The Active Directory and Windows System State backups are very similar. The key components that Recovery Manager for Active Directory backs up as part of the AD system state are the Registry, the NTDS.dit file, and SYSVOL.

What differences do they have?

• Windows System State backup is a full backup of the Windows operating system; Active Directory backup contains only pieces of Active Directory that allow you to restore the domain controller on a clean operating system.

• Windows System State backups contain more components - not all of these components are necessary for Active Directory recovery, e.g. IIS Metabase, Cluster Services, etc.

• Windows System State backup may contain viruses in the components of the operating system.

• Windows System State backups are larger than Active Directory backups.

For the list of Windows System State backup components, see Microsoft documentation.

Recovery Manager for Active Directory enables the backup and restoration of the following Active Directory components on domain controllers:

• DIT Database

• SYSVOL

• Registry, including all registry hives and the file NTUSER.DAT

Recovery Manager for Active Directory Disaster Recovery Edition also supports BMR backups. With BMR backups, you can completely rebuild the server if necessary.