Applies to: System Center 2022 Data Protection Manager
Introduction
This article describes the issues that are fixed in Update Rollup 3 for Microsoft System Center Data Protection Manager 2022. It 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. Recommended to update to latest version 2.0.9274.0 and above for better Online backups and restores.
Issues that are fixed
The update rollup 3 fixes the following issues:
-
DPM crashes when attempting to add a clustered VM to a new or existing PG on the Secondary DPM server.
-
DPM fails to perform Alternate Location Restore recovery of a VMware VM with disks excluded from backup.
-
Missing stored procedure prevents customer from fixing missing replica while using DPMSync tool.
-
Item-level Restore for VMware VMs may fail using online recovery points.
-
Item-Level Restore for a VMware VM fails with error 1001, using online recovery points.
-
InvalidRequestError raised while performing online restore of VMware VM's.
-
Recovery Point Status report is corrected to reflect disk and online restore points separate.
-
Restore of Hyper-V RCT VM, which live migrated from one host to another fails with error ID 958.
-
VMware DR backups intermittently fail with VDDKNotResponding error code.
-
Item-Level Restore fails for disks that contain a bit-locked volume.
-
VMware VMs may get power-off when in-progress backups are cancelled. Specific to VMware VM's running on vSphere 8.0 U2.
-
DPM Sync crashes when rebuilding DPM server from DPMDB which contains VMware protection information.
-
Schedule for the backup changes if retention range is modified.
-
Enabled online pruning by policy during DS removal from PG.
-
ContainerUsedSize for a Datasource was shown as negative in DPM Powershell.
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, UR1 Hotfix and UR2 Refresh are also included in SCDPM 2022 UR3.
Other Improvements and Features
-
SCDPM 2022 UR3 also has additional new features introduced. For details on the new features, refer to the documentation here.
How to obtain Update Rollup 3 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.
NOTE: MU update might fail initially as shown below or with a different error code. This is due to Visual C++ Redistributable updating runtime files existing on system and a restart is required to take the effect. If so, please restart the machine and try Install Updates one more time.There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x80070643)
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:
119591How to obtain Microsoft support files from online services
To install this update for Data Protection Manager Server, follow these steps:
1. Before you install this update, make a backup of the Data Protection Manager database.
2. Install this rollup package on the server that's running System Center Data Protection Manager 2022. To do this, from the downloaded bit run package "dataprotectionmanager-kb5059073_ce4e4e4b8dd358bd0b79e77235e9945dc96131fa.exe".
NOTE: Once the patch extracts, the Patch UI might not show-up. This is due to Visual C++ Redistributable updating runtime files existing on system and a restart is required to take the effect. If so, please restart the machine and try running package one more time.
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 Agent
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.
-
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 Center2022\DPM\DPM\agents\RA\10.22.425.0\amd64\1033\DPMAgentInstaller_KB5059073_AMD64.exe
-
Run the DPMAgentInstaller_KB5059073_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.425.0