Applies to: System Center Data Protection Manager 2022 Update Rollup 1
Introduction
This article describes the issues that have been fixed for System Center Data Protection Manager 2022 Update Rollup 1. This article also contains the installation instructions for this hotfix.
Issues fixed in this update
-
After updating to Update Rollup 1 for System Center Data Protection Manager 2022, backups for VMware VMs start failing with error "Disk SubSystem 0x80990EF1" for VMs that have VMware Tools installed due to a bug in Update Rollup 1.
Install this hotfix to fix the above issue. -
System Center Data Protection Manager 2022 RTM and Update Rollup 1 can't discover databases inSQL Server 2017 and 2016 over TLS 1.2.
This can happen after KB5021128 or KB5021127 is installed for SQL Server 2016 and 2017 respectively or when TLS 1.0 and 1.1 are disabled on the protected server.
This hotfix adds support for MSOLEDB 18 in the Data Protection Manager Agent for SQL Server 2017 & 2016 to enable discovery and protection over TLS 1.2. After applying this hotfix and updating the DPM Agent, you can install MSOLEDB 18 on the protected SQL Server 2017 and 2016 machine to ensure TLS 1.2 is used to discover and protect these servers.
Prerequisites
To apply this hotfix, you need to have Data Protection Manager 2022 or Update Rollup 1 for Data Protection Manager 2022 installed.
How to obtain Hotfix for Update Rollup 1 of System Center Data Protection Manager 2022
Hotfix package for Data Protection Manager is available only from download center for manual download. Download the hotfix here.
Files included in this Hotfix
DataProtectionManager-KB5026073.exe
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
To install this hotfix, follow these steps:
-
Download the hotfix to a target folder on your computer.
-
Open the target folder and do one the following based on your requirement:
-
Select and right-click DataProtectionManager-KB5026073.exe file to install the hotfix on the DPM server.
-
Select Run as administrator.
-
Accept the Microsoft Software License Terms, and then follow the steps in the installation wizard.
In the Data Protection Manager Administrator Console, update the protection agents. To do this, use one of the following methods.
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: agents\RA\10.22.158.0\amd64\1033\DPMProtectionAgent_KB5026073.msp
-
Run the DPMProtectionAgent.msp 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.158.0
Additional Instruction:
If you are running into issue #2 where you are unable to discover databases for protection after TLS 1.2 is enforced, after following the steps above to ensure the DPM Agent is up to date, you would also need to download and install MSOLEDB 18 on the protected SQL Server 2017 or 2016 to ensure discovery and protection is supported over TLS 1.2
Replacement Information
This hotfix does not replace any other previously released hotfix.
Restart Information
You need to reboot the DPM Server after installing the DPM hotfix.
