Recovery Manager for Active Directory (RMAD) 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)
For PowerShell® scripts launched from the domain controller side before and/or after creating a backup. (Scripts run from the Recovery Manager for Active Directory console are not supported)
Note |
Recovery Manager for Active Directory has deprecated support for a group managed service account (gMSA) to be specified as the account to connect to the backup agent for manually triggered backups. Managed service accounts will continue to be supported for scheduled backup tasks. In accordance with Microsoft®, it is recommended to not use a group managed service account (gMSA) for interactively initiated network connections such as Recovery Manager for Active Directory manually triggered backups. To enforce this recommendation and to address the vulnerability CVE-2023-21524 (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-21524), Microsoft has limited the usages of managed service accounts with a Windows Update. By removing support for a gMSA to connect to the backup agent, this ensures an attacker does not exploit the RMAD backup agent to perform actions or access resources over the network. To utilize the benefits and security provided by a group managed service account (gMSA), we highly recommend that a gMSA account is used for the scheduled backup task. See Setting user account for scheduled tasks |
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 RMAD machine.
How to create a Group Managed Service Accounts (gMSA)
Although the following instructions will configure gMSA accounts in your Active Directory® Forest, we recommend you first review the Microsoft® article: Getting Started with Group Managed Service Accounts
Note |
Even with the |
If you have never used gMSA accounts before, you must prepare Active Directory® by creating a KDS Root Key with one of the following PowerShell® commands on a domain controller:
In production, issue the command:
Add-KdsRootKey -EffectiveImmediately
In a test lab with minimal domain controllers, it’s safe to issue this command:
Add-KdsRootKey -EffectiveTime ((Get-Date).AddHours(-10))
Run this command once in each Domain of the Forest.
NOTE: For more information, see Create the Key Distribution Services KDS Root Key and this Microsoft Blog post.
(Optional) If you plan to use the same gMSA account on more than one host (for example, you have more than one RMAD server), then it may be easier to create a group for the hosts you plan to use it on. We suggest a Domain-Local Security group for this purpose. The following PowerShell® commands will create the group in the default Users container, then add your RMAD server as a member:
Add-ADGroupMember -Identity <GroupName> -Members <RMADServer$>
Repeat the command above for each RMAD server you want to use the gMSA account.
NOTE: If you use a group, then you must either restart the host(s) you added as members or run the command klist purge –li 0x3e7
on each host before performing step 4 below. This is to refresh the computer’s Kerberos ticket so it will include the new group SID in its NT Token.
Create the gMSA account using the following PowerShell command:
New-ADServiceAccount -Name <gMSAName> -DNSHost <gMSAName.domain> -PrincipalsAllowedToRetrieveManagedPassword <AccountName>
Where:
<gMSAName>
is the name of your gMSA account. For example: “gMSABackup”
<gMSAName.domain>
is the gMSA account followed by the domain. For example: “gMSABackup.contoso.com”
<AccountName>
is either <RMADServer$>
, or the group name you created in step 2 above.
NOTE: If using remote storage for backups, the account for each domain controller being backed up, needs to be added to the "PrincipalsAllowedToRetrieveManagedPassword" property for the gMSA account. Use the following command:
SetADServiceAccount -Identity <gMSAName>
-PrincipalsAllowedToRetreiveManagedPassword <AccountName>
.
After the gMSA account is created, you must install it on each host it will be used on (for example; on your RMAD server). Do this by running the following PowerShell® command on each host:
Install-ADServiceAccount -Identity <gMSAName>
(Optional) You can test that the gMSA account can be used by running the following PowerShell® command on each host where you installed the gMSA account:
Test-ADServiceAccount <gMSAName>
A result of True shows the gMSA account is ready to be used.
For more details, see Getting Started with Group Managed Service Accounts.
The Active Directory and Windows System State backups are very similar. The key components that Recovery Manager for Active Directory (RMAD) 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.
RMAD 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
RMAD Disaster Recovery Edition also supports Bare Metal Recovery (BMR) backups. With BMR backups, you can completely rebuild the server if necessary.
Recovery Manager for Active Directory (RMAD) allows you to create backups of system-specific data known as the Active Directory® and BMR backups. Note that RMAD creates Active Directory® backups for Active Directory® domain controllers only.
NOTE |
If you are going to store backups on the Recovery Manager Console machine, check that the Administrative Share "DriveLetter$" exists and is accessible on this host. Otherwise, the backup operation will fail. For more information, see Installing Backup Agent automatically. |
You can use Computer Collections to create backups for multiple computers. For more information, see Using Computer Collections.
NOTE |
When the backup is triggered and any specified backup path is not available, no backup is created, neither in the remote storage nor in the local storage. The backup creation session will fail. |
In the console tree, select a Computer Collection, and then click Create Backup on the Action menu.
If prompted, confirm the operation.
You can also use the Backup Wizard to start a backup job:
In the console tree, click the root node, and then click Create Backup on the Action menu.
Follow the instructions in the Backup Wizard.
On the When to Back Up page click Now, and then click Next.
Click Advanced to view backup options. You can modify the options as needed. When finished, click OK to close the Properties dialog box.
Click Finish to start the backup job.
Note |
By default, the wizard uses the default settings. You can view and modify the default settings using the Collection Defaults command that appears on the Action menu when you select the Computer Collections node in the console tree. |
With the Backup Wizard, backup jobs can be scheduled to run at a specific time. For more information, see Scheduling backup creation subsection of Task scheduler overview.
While a backup job is running, you can examine the progress of the operation and, if needed, stop the backup job. After a backup job is completed, you can view backup creation results:
In the console tree, click Sessions.
In the details pane, click the backup-creation session, and then click Properties on the Action menu.
In the Properties dialog box, click the Progress tab, and examine the displayed information.
By clicking Abort on the Progress tab, you can stop the selected session.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center