Update Rollup 2 for System Center 2022 Data Protection Manager

Introduction

This article describes the issues that are fixed in Update Rollup 2 for Microsoft System Center Data Protection Manager 2022. This article also contains the installation instructions for this update.

Note: Existing Data Protection Manager to Microsoft Azure customers should upgrade to the latest agent (version 2.0.9249.0 or later). If the latest agent is not installed, online backups may fail, and no Data Protection Manager to Microsoft Azure operation will work.

Note: Update Rollup 2 for System Center DPM 2022 is superseded by Update Rollup 2 Refresh for System Center DPM 2022 due to the following known issues:

Known issues:

Hyper-V scheduled backups take a long time to complete because each backup job triggers a consistency check. Error Message: The replica of Microsoft Hyper-V RCT on <Machine Name> is not consistent with the protected data source. DPM has detected changes in file locations or volume configurations of protected objects since the data source was configured for protection. (ID 30135)
Removing a data source from protection group or stopping backup results in an error with ID 33469, This operation is not supported on the current version of the MARS agent.
DPM console occasionally crashes when SMTP alerts or reports are configured.

Mitigation:

If you have already installed UR2 for SCDPM 2022, install UR2 Refresh for SCDPM 2022 to resolve the issues listed above.
If you have not installed UR2 for SCDPM 2022, install UR2 Refresh for SCDPM 2022 directly.

Reach out to Microsoft Support for queries or additional information.

Issues that are fixed

This update fixes the following issues:

Increase timeout of DPM Jobs and mount for online jobs to 30 days from 20 and 14 days respectively to enable backup of multi-TB data sources.
Restore of VM live migrated from Host A to Host B and back to Host A fails with ID 958.
Installing KB5021128 for SQL2016 or KB5021127 for SQL2017 prevents discovery of SQL databases for protection (was a part of DPM 2022 UR1 hotfix).
VMware backups fail with VMware Disk SubSystem 0x80990EF1 after applying DPM 2022 UR1 (was a part of DPM 2022 UR1 hotfix).
Hyper-V item level recoveries fail with ID 958, internal error code 0x80990F4E if recovery point could not be mounted.
Recovering file data from online recovery point to original location marks the replica as inconsistent.
BMR backup creates additional snapshot on the protected server.
Hyper-V backups does not remove avhdx files that are not required for backup.
Tape Backup of VMware VM does not backup .vmdk disk.
DPM occasionally crashes while enumerating volumes for protection.
DPM storage pool volumes are occasionally marked as missing due to failed WMI queries.
BMR backup sometimes fails with ID 104 - the process cannot access the file because it is being used by another process (0x80070020).
Hyper-V VM recovery fails with ID 104 - unexpected error occurred while the job was running, unknown error (0x80041024).
External DPM Server sometimes does not list all protected servers.
Reports email subject and body is not localized.
VMware VM restore fails with InvalidDeviceSpec error if networking configurations do not match for the source virtual distributed switches.
Recovering a VMware VM which has a disk excluded recovers all disks.
DPMSYNC command crashes after a server rebuild when VMware servers are protected.
Hyper-V VM backup and restore fail with ID 60, the protection agent was in an unexpected state, internal error code (0x809909B0).

Note: A fresh installation of the Update Rollup agent could cause a restart of the protected server.

In addition to the above fixes, all the issues fixed in SC DPM 2022 UR1 Hotfix are also included in SC DPM 2022 UR2.

Other Improvements and Features

SCDPM 2022 UR2 also has additional new features introduced. For details on the new features, refer to the documentation here.

Known issues

Stopping protection of a data source from fails with ID: 33469

Description: Removing a data source from protection group or stopping backup results in an error with ID 33469, “This operation is not supported on the current version of the MARS agent”.

This issue occurs because DPM erroneously checks for an installed version of MARS (Microsoft Azure Recovery Services) agent 2.0.9262.0 or later and fails when no MARS agent is available on the DPM server.

Workaround: Download and install the Microsoft Azure Recovery Services (MARS) agent on your DPM Server. You need not register the MARS agent to Azure. Installation mitigates this error.

To install MARS, follow these steps:

Download the latest agent..
Double click MARSAgentInstaller.exe.
Retain the default installation and cache folders and then select Next.
Retain the default proxy settings and select Next.
Review the prerequisites and select Install.
After agent installation, close the installation wizard and check if the issue is mitigated.

Retry removing the data source after installation of MARS. If the issue persists, reach out to Microsoft support.

How to obtain Update Rollup 2 for System Center Data Protection Manager 2022

Update packages for Data Protection Manager are available from Microsoft Update or by manual download.

Microsoft Update

To obtain and install an update package from Microsoft Update, follow these steps on a computer that has a Data Protection Manager component installed:
Select Start, and then select Control Panel.
In Control Panel, double-click Windows Update.
In the Windows Update window, select Check Online for updates from Microsoft Update.
Select Important updates are available.
Select the Update Rollup package, and then select OK.
Select Install updates to install the update package.

Manual download

Go to the following website to manually download the update package from the Microsoft Update Catalog: Download the Data Protection Manager update package now

For information about how to download Microsoft support files, select the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services

Virus-scan claim

Microsoft scanned this file for viruses, using the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to it.

Installation instructions for Data Protection Manager

To install this update for Data Protection Manager, follow these steps:

Before you install this update, make a backup of the Data Protection Manager database.
Install this rollup package on the server that's running System Center Data Protection Manager 2022. To do this, run Microsoft Update on the server.
In the Data Protection Manager Administrator Console, update the protection agents. To do this, use one of the following methods.

Note: You need to restart protected servers to create or change protection groups.

Method 1: Update the protection agents from the Data Protection Manager Administrator Console

Open the Data Protection Manager Administrator Console.
Select the Management tab, and then select the Agents tab.
1. In the Protected Computer list, select a computer, and then select Update on the Action pane.
Select Yes, and then select Update Agents.

Method 2: Update the protection agents on the protected servers

Obtain the updated protection agent package from the installation directory of the System Center Data Protection Manager 2022 server at following path: Microsoft System Center 2022\DPM\DPM\agents\RA\10.22.189.0\amd64\1033\DPMAgentInstaller_KB5032420_AMD64.exe
Run the DPMAgentInstaller_KB5032420_AMD64.exe package on each protected server.
Open the Data Protection Manager Administrator Console on the System Center Data Protection Manager server 2022.
Select the Management tab, and then select the Agents tab. Select the protected server, refresh the information, and then verify that the agent version number is 10.22.189.0