This article describes the issues that are fixed in Update Rollup 5 for Microsoft System Center 2012 R2 Data Protection Manager. Additionally, this article contains the installation instructions for Update Rollup 5 for System Center 2012 R2 Data Protection Manager.
Issues that are fixed in this update rollup
- In some cases, an update rollup installation failure may revert back to an older Data Protection Manager database. For example, as part of the installation for an update rollup, Data Protection Manager makes a backup of the Data Protection Manager database by default. If for some reason the backup of the Data Protection Manager database fails, Data Protection Manager would terminate the installation and try to roll back to the previously installed update rollup. In some cases, Data Protection Manager would revert back to an older version of the Data Protection Manager database which might lead to a loss of some recent Data Protection Manager configuration changes.
- Tape backup of millions of files fails with error “ID 998 Details: The parameter is incorrect (0x80070057).”
- Restoring a SharePoint Server hostname site collection fails with error “Index was outside the bounds of the array.. (ID 32017 Details: Unknown error (0x80131508) (0x80131508)).”
- You cannot obtain a list of active recovery points by using Windows PowerShell. For example, the Data Protection Manager Windows PowerShell command Get-DPMRecoveryPoint displays all the recovery points. This includes both active and expired recovery points. The new option Get-DPMRecoveryPoint -Only Active displays a list of only active (that is, non-expired) recovery points. The original command can still be used to obtain all the recovery points.
- If autoheal is enabled for SharePoint Server with multiple databases but backup for a few databases fails, Data Protection Manager skips those databases and creates a recovery point. However, Data Protection Manager does not display any alert for the skipped databases, and the only way to check the missing databases is to browse through the recovery point. With this fix, an alert is raised whenever any content database is skipped.
- While it tries to set up a library sharing server, Data Protection Manager displays the following error message:
Failed to execute SharedLibraryConfigureDb.sql on local_dpm_server_name
- You cannot recover data after you change the bar code of a tape. For example, Data Protection Manager may sometimes be unable to recover data from imported tapes, especially if the bar codes of the tapes were modified. With this update, Data Protection Manager will always be able to recover data, even from imported tapes.
- The Data Protection Manager UI crashes intermittently when a backup to tape is performed.
- Backup job for dedupe-enabled volume on Windows 2012 R2 fails. For example, Data Protection Manager backup might fail for following setup:
- Data Protection Manager2012 R2 is installed on Windows Server 2012.
- Data Protection Manager is protecting a dedupe-enabled volume on Windows Server 2012 R2.
- The DPMVmmHelper Service is set to DISABLED every time that a Data Protection Manager update rollup is installed. For example, during installation, the Data Protection Manager Update Rollup DPMVmmHelper service is disabled, and the backup will fail if a virtual machine is migrated outside a cluster unless service is enabled manually. With this update, Data Protection Manager retains the state of the service while the update is installed. (This applies to Update Rollup 5 and later updates.)
- When the Data Protection Manager UI crashes, it brings down the entire Microsoft Management Console (MMC) snap-in. This affects other processes if there are multiple MMC snap-ins. For example, when Data Protection Manager is started as a snap-in the mmc.exe process and there is any issue with the Data Protection Manager UI, the entire snap-in is brought down. This affects other processes. With this update, when the Data Protection Manager MMC snap-in is reloaded, no other process are affected. Additionally, the Connection to DPM service has been lost popup was changed. Specifically, we removed the option to restart the Data Protection Manager console, because the console is automatically restarted.
- Improved inquiry performanceWith this update, Data Protection Manager brings speed improvements to the inquiry step in the Create/Modify Protection Group wizard. This is accomplished by the persistent caching of data sources, the pruning of unused inquiry data during nightly database cleanup, and a more optimized inquiry on servers that have clustered virtual machines on CSV volumes.
Therefore, the behavior of the wizard changed. The Clear Cache button is replaced with the Refresh button, and expanding a production server in the selection page now instantly obtains the data sources from the last inquiry that are cached in the database without actually triggering an inquiry on the production server. To trigger a fresh inquiry to obtain the latest data sources (and to update the cache), you have to click Refresh after you select the production server.
For more info., you can check below link