Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Applies to: System Center 2019 Data Protection Manager


This article describes the issues that are fixed in Update Rollup 4 for Microsoft System Center Data Protection Manager 2019. 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 a later version). If the latest agent is not installed, online backups may fail, and no Data Protection Manager to Microsoft Azure operation will work.

Issues that are fixed

This update fixes the following issues:

  • Restoring tapes with DPM 2019 UR3 for VMware VMs results in boot failure

  • BMR backup is not handling replica creation correctly, results in running out of disk space

  • DPM 2019 does not detect resilient change tracking (RCT)

  • Online restore fails due to missing data source volume mapping

  • DPM2019 UI crashes when searching files and folders under recovery

  • Unable to deploy or attach agent with Smart Card Authentication

  • Post backup script fails to execute

  • Unable to delete online data sources from either inactive or active protection group (due to malfunction of PIN functionality) while using Central Console

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

Other Improvements and Features

  • SCDPM 2019 UR4 also has additional new features introduced. For details on the new features refer to the documentation here.

Known issues

Known issue 1

If you are using secondary DPM server, you might see sync jobs failing on Secondary DPM server for the primary DPM replica protection group. See the bottom of this page to learn more.

Known issue 2

If you are using DPM 2019 UR3 and using Remote UI or Central Console, please uninstall DPM 2019 UR3 and then install DPM 2019 UR4. This is applicable to Remote UI and Central Console based usage only. There is no issue with installing UR4 on DPM Servers.

How to obtain Update Rollup 4 for System Center Data Protection Manager 2019

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

Microsoft Update

  1. To obtain and install an update package from Microsoft Update, follow these steps on a computer that has a Data Protection Manager component installed:

  2. Click Start, and then click Control Panel.

  3. In Control Panel, double-click Windows Update.

  4. In the Windows Update window, click Check Online for updates from Microsoft Update.

  5. Click Important updates are available.

  6. Select the Update Rollup package, and then click OK.

  7. Click 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, click the following article number to view the article in the Microsoft Knowledge Base:
119591How 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:

  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 2019. To do this, run Microsoft Update on the server.

  3. 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 in order to create or change protection groups.

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

  1. Open the Data Protection Manager Administrator Console.

  2. Click the Management tab, and then click the Agents tab.

  3. In the Protected Computer list, select a computer, and then click Update on the Action pane.

  4. Click Yes, and then click Update Agents.

Method 2: Update the protection agents on the protected servers

  1. Obtain the updated protection agent package from the installation directory of the System Center Data Protection Manager 2019 server at following path: agents\RA\10.19.577.0\amd64\1033\DPMProtectionAgent_KB5014054.msp

  2. Run the DPMProtectionAgent.msp package on each protected server.

  3. Open the Data Protection Manager Administrator Console on the System Center Data Protection Manager server 2019.

  4. Click the Management tab, and then click the Agents tab. Select the protected server, refresh the information, and then verify that the agent version number is 10.19.577.0

More information

For fixing the issue related to failing sync jobs on your secondary DPM server for the primary DPM replica protection group, you need to enable the registry key mentioned below and run a consistency check for the same data source.

Registry Key: HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration\ParallelMountDismountSettings\MountUsingWMIQuery
Value: 1

Script to add reg key:
reg add "HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration\ParallelMountDismountSettings" /v MountUsingWMIQuery /t REG_DWORD /d 1 /f

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!