This article describes the issuesthat are fixed in Update Rollup 8 for Microsoft System Center 2016 DataProtection Manager. This article also contains the installationinstructions for this update.
Note ExistingData Protection Manager to Microsoft Azure customers should upgrade to thelatest agent (version 2.0.9169.0 or a later version). If the latest agent isnot installed, online backups may fail, and no Data Protection Manager toWindows Azure operation will work.
Issues that are fixed
This update fixes the followingissues:
- Data Protection Manager service crash with error "The directory is not empty" while failing to delete a replica path during the Garbage Collection process.
- Restore Operation for SQL workloads fails with an error “Consolidation of recovery points of the replica failed” due to timeout. Introduced registry key to extend timeout value. Refer More Information section for additional details.
- The backup operation fails when Certificate based authentication is configured and Null Ciphers are disabled
- SharePoint backup fails when SQL server is different domain. Refer More Information section for additional details.
Note A fresh installation of theUpdate Rollup Agent could cause a restart of the protected server.
How to obtain Update Rollup 8 for System Center 2016 Data Protection Manager
Update packages for Data ProtectionManager are available from Microsoft Update or by manual download.
To obtain and install an updatepackage from Microsoft Update, follow these steps on a computer that hasa Data Protection Manager component installed:
- Click Start, and then click Control Panel.
- In Control Panel, double-click Windows Update.
- In the Windows Update window, click Check Online for updates from Microsoft Update.
- Click Important updates are available.
- Select the Update Rollup package, and then click OK.
- Click Install updates to install the update package.
Go to the following website tomanually download the update package from the Microsoft Update Catalog:
For information about how todownload Microsoft support files, click the following article number to viewthe article in the Microsoft Knowledge Base:
119591 Howto obtain Microsoft support files from online services
Virus-scanclaimMicrosoft scanned this file for viruses, usingthe most current virus-detection software that was available on the date thatthe file was posted. The file is stored on security-enhanced servers that helpprevent any unauthorized changes to it.
Installation instructions for Data Protection Manager
To install this update for DataProtection 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 2016 Data Protection Manager. 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: Thisupdate rollup agent update requires you to restart protected servers to createor change protection groups.
Method 1:Update the protection agents from the Data Protection Manager AdministratorConsole
- Open the Data Protection Manager Administrator Console.
- Click the Management tab, and then click the Agents tab.
- In the Protected Computer list, select a computer, and then click Update on the Action pane.
- Click Yes, and then click Update Agents.
Method 2:Update the protection agents on the protected servers
- Obtain the update protection agent package from the following directory on the System Center 2016 Data Protection Manager server:
- The installation packages are as follows:
Restore operation of SQL backup may fail with an error“Consolidation of recovery points of the replica failed” due to timeout. Toresolve this issue, make sure you install this UR. Then add following registrykey to increase the timeout value. The default value is 30 minutes. You can increase up to 300 minutes.
Addthe following registry key on the DPM server to increase the timeout value
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MicrosoftData Protection Manager\Configuration\DiskStorage
Ifthe SQL Database server for SharePoint farm is in different domain thanSharePoint farm, the protection of SharePoint farm may fail. This happens whenthe NetBIOS name of SQL server was used during SharePoint installationinstead of FQDN. To resolve this issue either you can reinstallSharePoint farm by specifying FQDN of the SQL Server or use followingregistry key. You first need to install this Update Rollup package on the DPM Server
Addthe following registry key on all the SharePoint Web Front End Servers,
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MicrosoftData Protection Manager\Agent\Sharepoint
Type:StringValue: <Domain name of the SQL Server>