Update Rollup 2 for System Center 2019 Data Protection Manager

Introduction

This article describes the issues that are fixed in Update Rollup 2 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 apply the mandatory update of Microsoft Azure Recovery Services (MARS) agent version 2.0.9190.0 or above and verify the encryption passphrase using the steps provided in this KB article. If the latest agent is not installed, online backup and recovery may fail, and no Data Protection Manager to Microsoft Azure operation will work.

Issues that are fixed

This update fixes the following issues:

  • A stale file entry in the ActiveOwner folder breaks VMware protection.

  • Bare metal backups running longer than 24 hours will time out. Registry key added to the protected server to extend the timeout: Refer Issue 1 in More Information section for more details.

  • Disk Utilization Report was not reflecting Modern Backup Storage usage.

  • In some scenarios, re-protecting an inactive workload re-calculates the required disk space to be excessively large

  • In SQL Always On configuration with a Failover cluster backup, sometimes the backups will fail because the backup preferences are not honored.

  • Modify Protection Group operation may take a long time, while protecting large number of client machines in a single protection group

  • Pre and Post Backup scripts don’t work with RCT based Hyper-V workloads

  • Consistency check for deduped enabled NTFS volumes fails with error: ID 30134 Details: Cannot create a file when that file already exists (0x800700B7)

  • SharePoint backup fails when SQL server is different domain than the front-end SharePoint server. Refer Issue 2 in More Information section for additional details.

  • In Modify Protection group wizard, changing retention settings will result in changes to the backup schedule

  • DPM console crashes when attempting restore with throttling on clustered VMs

  • Hyper-V VM protection fails when the total size of the VM file name and DPM mount path is more than 256 characters

  • If a vCenter server is protected with a Windows agent, and if the same server is added as a VMware server, the console crashes

  • If the remote DPM UI version is lower than the DPM version, the remote UI may crash

  • In some cases, the DPM UI can become unresponsive on the Protection tab and while browsing through protection groups

  • In addition to these, all the issues fixed in SC DPM 2016 Update Rollup 9 and prior UR for DPM 2016 are also included in SC DPM 2019 UR2.

Other Improvements and Features

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

Known Issues

  • Sometimes, DPM console might not display Protection Group details in the Details pane. Learn more.

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

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

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:

  1. Click Start, and then click Control Panel.

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

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

  4. Click Important updates are available.

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

  6. 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:

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:

  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.379.0\amd64\1033\DPMProtectionAgent_KB4563392.msp

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

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

  3. 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.379.0



More information

Issue 1

Bare metal backups running longer than 24 hours will time out. To resolve this issue, make sure you install this UR. Then add following registry key to increase the timeout value. The default value is 24 hours. You can increase up to 72 hours.

Add the following registry key on the protected server to increase the timeout value

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Workloads\System State Writer

Name: PreSnapShotScriptTimeout

Type: REG_DWORD

Value: 48

Issue 2

If the SQL Database server for SharePoint farm is in different domain than SharePoint farm, the protection of SharePoint farm may fail. This happens when the NetBIOS name of SQL server was used during SharePoint installation instead of FQDN. To resolve this issue either you can reinstall SharePoint farm by specifying FQDN of the SQL Server or use following registry key. You first need to install this Update Rollup package on the DPM Server

Add the following registry key on all the SharePoint Web Front End Servers,

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent\Sharepoint

Name: AlternateDomainForDatabaseServer

Type: String

Value: <Domain name of the SQL Server>

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×