System Center DPM Release Notes

  • Article
  • 28 minutes to read

This article lists the release notes for System Center 2019 - Data Protection Manager (DPM), includes the known issues and workarounds for DPM 2019, DPM 2019 UR1,and DPM 2019 UR2, as applicable.

We recommend you to see the following articles for detailed information about what DPM supports and can back up:

This article lists the release notes for System Center 2022 - Data Protection Manager (DPM), includes the known issues and workarounds for DPM 2022.

We recommend you to see the following articles for detailed information about what DPM supports and can back up:

DPM 2022 release notes

DPM 2022 has the known issues that are observed in DPM 2019 RTM, UR1 and UR2. In addition, the following known issues are observed.

Upgrade from DPM 2019 to DPM 2022 might fail when the DPM database name is DPMDB

Description: If the name of the existing DPM database is DPMDB, the upgrade will fail.

The DPM upgrade process will always rename the DPM database name to DPMDB. If the same SQL instance is used by multiple DPM servers, the subsequent upgrade of the other DPM server will fail as there is already a database with the name DPMDB.

Workaround: Rename the corresponding DPM database before you start the upgrade.

Use these steps to rename the database:

  1. Stop the DPM service on the DPM server.

  2. Run the following SQL commands to rename the database, update the DPM server name in the query below.

    USE master
GO
ALTER DATABASE DPMDB  
SET SINGLE_USER  
WITH ROLLBACK IMMEDIATE
GO
EXEC master..sp_renamedb 'DPMDB','DPMDB_<DPMSERVERNAME>'
GO
ALTER DATABASE DPMDB_<DPMSERVERNAME>
SET MULTI_USER  
GO

  3. Update the following registry keys to reflect the updated database name.

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\DB\ConnectionString

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\DB\DatabaseName

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\DB\GlobalDatabaseName

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\DB\GlobalDbConnectionString

    Screenshot showing registry editor that reflects the database name.

  4. Run DPMsync on the DPM server using DPM management shell.

    DPMSync -Sync

Online recovery point creation of a datasource might fail with error ID 33505 or 100195

Description: In some scenarios the online recovery point creation of a datasource may fail intermittently with error ID 33505 or 100195.

Screenshot showing error when creating online recovery point.

Screenshot showing error message when creating online recovery point.

Workaround:

  1. Upgrade the MARS agent to the latest version.

  2. Retry the online backup for the failed datasource.

  3. Create a new disk recovery point and then try the online recovery point again.

  4. Run the consistency check and try the online backup again.

  5. If the online backup is still failing, contact the support team.

Important

This version of Data Protection Manager (DPM) has reached the end of support, we recommend you to upgrade to DPM 2019.

This article lists the release notes for System Center 1807 - Data Protection Manager (DPM).

Important

This version of Data Protection Manager (DPM) has reached the end of support, we recommend you to upgrade to DPM 2019.

This article lists the release notes for System Center 1801 - Data Protection Manager (DPM).

This article lists the release notes for System Center 2016 - Data Protection Manager (DPM).

DPM 2019 release notes

The following sections summarize the release notes for DPM 2019 and include the applicable known issues and workarounds.

DPM console crashes due to MSDPM Service crash

Description: Presence of duplicate summary management jobs, after DPM upgrade, might lead to failure of any in-progress jobs at zero hours eventually leading to a crash. As a result, you might observe the following:

  • Replica is inconsistent.
  • Storage bloat caused due to non-deletions of recovery points.
  • Outdated DPM reports.
  • No clean-up for job history and garbage collection jobs.

Workaround:

  1. Back up the current DPM database.

  2. Open SQL management studio and connect to the SQL Instance hosting the DPMDB for this server.

  3. Run the following query, and check if you have two or more summary manager jobs scheduled, and see which the older schedule was:

     SELECT SCH.ScheduleId, SCH.JobDefinitionId, jd.CreationTime
 FROM tbl_JM_JobDefinition JD
 JOIN tbl_SCH_ScheduleDefinition SCH
 ON JD.JobDefinitionId = SCH.JobDefinitionId
 WHERE JD.Type = '282faac6-e3cb-4015-8c6d-4276fcca11d4'        
 AND JD.IsDeleted = 0
 AND SCH.IsDeleted = 0

  4. If you have more than one row returned, take the resulting ScheduleID and JobDefinitionID of the older entry and mark them as deleted.

     update tbl_SCH_ScheduleDefinition
 set IsDeleted = 1
 where ScheduleId = ‘ScheduleID '               --- Replace with Your ScheduleID
 update dbo.tbl_JM_JobDefinition
 set IsDeleted = 1
 where JobDefinitionId = ‘JobDefinitionID'             --- Replace with Your JobDefinitionID

  5. Delete the SQL job that is matching the ScheduleID under the SQL Server Agent – JOBS. Once deleted, the crash at zero hours would be resolved.

    ScheduleId is the SQL Jobs under SQL agent:

    UPDATE MSDB.dbo.sysjobs
SET Enabled = 0
WHERE [Name] LIKE ‘ScheduleID’  --- Replace with Your ScheduleID

Hyper-V VMs are protected twice on VM upgrade

Description: When upgrading a Hyper-V VM from Windows Server 2012 R2 to Windows Server 2016, two versions of the VM appear in the Create Protection Group wizard.

Workaround: For the protected VMs which are about to be upgraded, make sure to stop protection with retain data before upgrading the VM. Then, upgrade the VM and reprotect it in a new protection group. While configuring reprotection, do a refresh on the VM host for DPM to detect the VM upgrade and protect it as RCT VM.

Restoration of a previous version for an upgraded Hyper-V VM causes future recovery points to fail

Description: When you upgrade a protected 2012 R2 Hyper-V VM to the 2016 version, then stop protecting the VM (but retain data), and then re-enable protection, if you then recover a 2012 R2 copy at the original location, further backups might fail.

Workaround: After recovery, change the VM version to 2016, then run a consistency check.

Bare Metal Recovery protection failures

Description: If you configure Bare Metal Recovery (BMR) protection, the BMR protection job might fail with the message that the replica size is not sufficiently large.

Workaround: Use the following registry path to change the default replica size for BMR data sources. Open the registry editor and increase the replica size for the following key:

HKLM\Software\Microsoft\Microsoft Data Protection Manager\ConfigurationReplicaSizeInGBForSystemProtectionWithBMR (DWORD)

DPM database protection stops in case of upgrade scenarios

Description: When you upgrade DPM, database name might change in some scenarios.

Workaround: If you are protecting a DPM database, ensure to enable the protection for the new DPM database. Once the DPM upgrade is validated, you can remove protection for the previous DPM database.

Hyper-V RCT - recover as files for D-T backup fails

Description: Recovery of Hyper-V RCT VMs as files created directly on tape (D-T) fails. D-D-T backups do not exhibit this issue.

Workaround: Use Alternate Location Recovery as a VM, and then transfer those files to the desired location.

Note

This feature is fixed in DPM 2019 UR1. You can install UR1 to get this issue fixed. For detailed information about installing UR1, see the KB article for UR1.

DPM 2019 does not support file server end user recovery with Modern Backup Storage (MBS)

Description: DPM 2019 does not support end user recovery with Modern Backup Storage (MBS).

Workaround: None. File Server EUR is not supported when using MBS.

DPM 1801/1807 servers cannot be managed by DPM 2019 central console

Description: With DPM 2019 central console you cannot manage any DPM 1801 or DPM 1807 servers.

Workaround: Upgrade your DPM server to version 2019.

Recovery Points not being pruned, leading to an accumulation of Recovery Points

Description: DPM prunes recovery points older than the retention range. During the pruning process, DPM calculates the storage consumed by those recovery points to be pruned. Storage calculation delays pruning.

Workaround: Configure DPM to skip calculating the size of recovery points to be pruned. As a result, the pruning script runs faster, and prunes all recovery points older than the retention range, relieving any storage pressures. The storage consumed per data source isn't updated until DPM finishes pruning. The storage consumption per volume continues to reflect the correct values. Use a PowerShell script to turn on size calculation. The following script runs complete size calculations.

Location: Program Files\Microsoft System Center\DPM\DPM\bin\Manage-DPMDSStorageSizeUpdate.ps1

Script: Manage-DPMDSStorageSizeUpdate.ps1 -ManageStorageInfo [StopSizeAutoUpdate | StartSizeAutoUpdate | GetSizeAutoUpdateStatus | UpdateSizeInfo ] [-UpdateSizeForDS <FilePath>] [-UpdatedDSSizeReport <FilePath>] [-FailedDSSizeUpdateFile <FilePath>]

  • ManageStorageInfo: - Specifies the kind of operation needed.

    • StopSizeAutoUpdate: Stops the size calculations completely. Both UI and PowerShell will not report sizes.

    • StartSizeAutoUpdate: Resumes the size calculations. Immediately after enabling size calculations, use UpdateSizeInfo (in the following options) to recalculate sizes for all the datasources, until which sizes reported in PowerShell and UI may not be correct.

    • GetSizeAutoUpdateStatus: Tells whether size calculations are enabled or disabled.

    • UpdateSizeInfo: Triggers the size calculation and reports the size consumed by datasource. As this can be a long-running operation, use it only when needed, for scenarios such as billing. During this time, backups may fail with vhd mount errors.

  • UpdateSizeForDS: Path to a text file with a list of Datasource IDs for which size needs to be calculated, with a datasourceID on each line. When not passed, size calculation is triggered for all the datasources. Use after using UpdateSizeInfo in ManageStorageInfo. To get the Datasource IDs of specific datasources, use Get-DPMProtectionGroup | Get-DPMDatasource | Format-table -Property Computer,name,ObjectType,Id.

  • UpdatedDSSizeReport: Path to a file that stores the updated datasource sizes. When not passed sizes.csv, a file is created in the execution directory. Use after UpdateSizeInfo in ManageStorageInfo.

  • FailedDSSizeUpdateFile: Path to a file to store the Datasource IDs for the datasources for which the storage consumption couldn’t be calculated. This may happen due to reasons as ongoing backups. When not passed failedDS.txt file is created in the execution directory. This file can be given as input to “UpdateSizeForDS” to update the sizes of all the datasources. This should be used after using UpdateSizeInfo in ManageStorageInfo.

DPM Datasources not being reflected on Recovery Services Vault

Description: Some datasources in the Backup items (DPM) view from recovery service vault in Azure portal, are not getting refreshed/updated.

Cause: You may have decommissioned a protected server and stopped protection of the datasources but chose to maintain the online recovery points, then you un-installed the DPM/MABS agent from the console.

You can verify if this is the cause by opening the GatewayProvider0Curr.errlog file in C:\ProgramFiles\Microsoft Azure Backup Server\DPM\MARS\Temp folder in notepad and search for the word Mis-Match.

If you find an entry as the following, it will detail the protected server that is mis-matched.

In the below example, the agent for the server called mjlc-dc.Contoso.com was un-installed and missing from the DPM/MABS server.

GetData of Provider failed. |Backup Service Exception: FMException: [ErrorCode:GPPowershellScriptHrError, DetailedCode:-2146233079, Source:   at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord), Message:Production Server **mis-match** DSId :9adaec12-5b5a-455e-86b9-1fac2d605fe1 DSName : S:\ DSType : Volume PSName :**mjlc-dc.Contoso.com** PSId: a494f940-b480-41d2-9ef5-4194ad737c7b]

Workaround

  1. If the original protected server is still available, re-install the DPM agent even if you plan on taking that server offline in the future. You can disable the agent in DPM/MABS, don’t remove it until you delete the online recovery points.
  2. If the online recovery points for the decommissioned server are no longer needed, then you can delete the data sources on the DPM/MABS server that are in stopped protection.

DPM 2019 UR1 release notes

VM restore with excluded disk (to alternate host) restores empty disk

Description: Restoring the VM with excluded disk to alternate host will restore the excluded disk as empty disk. The excluded disk will not be attached to VM. The disk can be deleted to save the storage space.

Workaround: None

For issues fixed in DPM 2019 UR1, see the KB article.

DPM 2019 UR2 release notes

The following sections detail the known issues and workarounds for DPM 2019 UR2.

For issues fixed in DPM 2019 UR2, see the KB article.

Protection group details are not displayed in DPM console

Description: After installing DPM 2019 UR2, sometimes, DPM console might not display Protection Group details in the Details pane.

console with no details for Protection Group

Workaround: Use Get-DPMProtectionGroup PowerShell command to view the Protection Group details.

Note

This issue is fixed in DPM 2019 UR3. For more information about the issues fixed in UR3, see the KB article.

Latest report files are not automatically updated

Description: With DPM 2019 UR2, issue with DPM report formatting and volume to volume migration reporting is fixed. However, the existing report files are not automatically replaced with the updated files.

Workaround: Follow these steps to replace the existing report files:

Replace the ReportSRV10.dll

  1. Stop the SQL Server Reporting service
  2. Select the updated ReportSRV10.dll file present in C:\Program Files\Microsoft System Center\DPM\DPM\bin and replace the existing DLL files in the following folders:
    • For SQL Server 2017 and later - C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\bin
    • For SQL Server 2016 - C:\Program Files\Microsoft SQL Server\MSRS13.MSDPM2012\Reporting Services\ReportServer\bin
  3. Start the SQL Server Reporting service.

Replace the RDL files

  1. On DPM, open the SQL Reporting Services portal URL.

  2. On the portal, the DPMReports folder is present in the format DPMReports_<GUID>.

    Reports folder

    Note

    You can see only one folder with this naming convention. If DPM is upgraded from a previous version, the previous folder might still exist, but you can’t open it.

  3. Select and open the DPMReports_<GUID> folder. The individual report files are displayed.

    List of individual report files

  4. Select the report files that don't end with Report, right-click Option, and then select Manage.

    Manage report files

  5. In the new page, select Replace to replace with the latest report files.

    Replace report files

    The latest report files are available in the DPM installation path:

    For example: C:\Program Files\Microsoft System Center\DPM\DPM\bin\DpmReports

  6. After the files are replaced, ensure that the Name and Description are intact and aren't empty.

  7. Restart DPM and use the report files.

DPM 2019 UR3 release notes

The following section details the known issue in DPM 2019 UR3 and the workaround.

DPM Remote console might fail to connect to DPM server, after upgrading to Update Rollup 3

Description: After upgrading DPM Remote Administration Console to Update Rollup 3, it might fail to connect to DPM server with an error “The DPM Administrator Console version is incompatible with the DPM server version”

Workaround:

  1. On the server running DPM Remote Administration console, run the following PowerShell command (enter the DPM server name as applicable), this command copies the required DLL files from the DPM server:

    $RemoteUIPath = "C:\Program Files\Microsoft Data Protection Manager\DPM2019\bin"
$RemoteUidlls = Get-Item "$RemoteUIPath\*" | ? {$_.name -match ".dll"}
Write-Host -MessageData "Copying required $($RemoteUidlls.count) DLL's for Remote UI"
foreach ($dll in $RemoteUidlls) {
Copy-Item -Path "\\<FQDN of the DPM Server>\c$\Program Files\Microsoft System Center\DPM\DPM\bin\$($dll.name)" -Destination $RemoteUIPath
}
$RemoteUIUR3Dlls = "Microsoft.ApplicationInsights.dll",
"Microsoft.Diagnostics.Tracing.EventSource.dll",
"Microsoft.SystemCenter.DPM.Instrumentation.dll",
"Microsoft.SystemCenter.DPM.InstrumentationScheduler.dll",
"Microsoft.SystemCenter.Instrumentation.dll",
"Microsoft.WindowsAzure.Storage.dll",
"Newtonsoft.Json.dll"
foreach ($dll in $RemoteUIUR3Dlls) {
$SourceDllPath = "\\<FQDN of the DPM Server>\c$\Program Files\Microsoft System Center\DPM\DPM\bin\" + $dll
Copy-Item -Path $SourceDllPath -Destination $RemoteUIPath
}
Write-Host -MessageData "All required DLL files for DPM Remote UI UR3 has been copied"

    Note

    If you are using DPM Remote UI on a SCOM machine then copy for below files might fail, this can be ignored.

    • SCOMHelperLibrary.dll
    • ScopingCommonHelper.dll
    • ViewAlertsAndAffectedItemsHelper.dll
    • Wpfhelpers.dll

  2. If you are using a language different than English, copy the respective language folder from the DPM server. Update the DPM server name and language folder in the following command, and then run the command.

    Copy-Item -Path \\<FQDN of the DPM_Server>\c$\Program Files\Microsoft System Center\DPM\DPM\bin\<Language folder>\*.dll -Destination C:\Program Files\Microsoft Data Protection Manager\DPM2019\bin\<Language folder>

    Note

    This command uses the default installation path for DPM. If you have changed the installation path, update the path accordingly.

DPM 1807 Release notes

To view the list of bugs that have been fixed in DPM 1807, refer to KB article 4339950.

The following issues exist in the 1807 release.

Hyper-V VMs are protected twice on VM upgrade

Description: When upgrading a Hyper-V VM from Windows Server 2012 R2 to Windows Server 2016, two versions of the VM appear in the Create Protection Group Wizard.

Workaround: For the VMs that haven't been upgraded, stop protection with Retain Data. Upgrade the VM, and create a new protection group. Then refresh the data sources, and protect the VMs. When you reapply protection, the VMs are protected using Resilient Change Tracking (RCT).

Agent installation fails on Windows Server 2008, Windows Server 2008 R2

Description: When protecting Windows Server 2008, or Windows Server 2008 R2, installing the agent can fail.

Workaround: Upgrade the Windows Management Framework (WMF) on the production server to 5.1. Download the WMF from Windows Management Frame 5.1. Install WMF and then install the agent.

Restoring a previous version of an upgraded Hyper-V VM causes future recovery points to fail.

Description: If you upgrade a protected 2012 R2 Hyper-V VM to the 2016 version, then stop protecting the VM (but retain data), and then re-enable protection, if you then recover a 2012 R2 copy at the original location, further backups may fail.

Workaround: After recovery, change the VM Version to 2016, then run a Consistency Check.

Bare Metal Recovery protection failures

Description: If you configure Bare Metal Recovery (BMR) protection, the BMR protection job may fail with the message that the replica size is not sufficiently large.

Workaround: Use the following registry path to change the default replica size for BMR data sources. Open the registry editor and increase the replica size for the following key:

HKLM\Software\Microsoft\Microsoft Data Protection Manager\ConfigurationReplicaSizeInGBForSystemProtectionWithBMR (DWORD)

Reprotecting the DPM database after upgrading to DPM 2016 or 1801

Description: When you upgrade from System Center DPM 2012 R2 to System Center Data Protection Manager 2016 or 1801, the DPM database name can change in some scenarios.

Workaround: If you are protecting a DPM database, be sure to enable protection for the new DPM database. Once the DPM upgrade is validated, you can remove protection for the old DPM database.

Recovery Points not being pruned, leading to an accumulation of Recovery Points

Description: DPM prunes recovery points older than the retention range. During the pruning process, DPM calculates the storage consumed by those recovery points to be pruned. Storage calculation delays pruning.

Workaround: Configure DPM to skip calculating the size of recovery points to be pruned. As a result, the pruning script runs faster, and prunes all recovery points older than the retention range, relieving any storage pressures. The storage consumed per data source isn't updated until DPM finishes pruning. The storage consumption per volume continues to reflect the correct values. Use a PowerShell script to turn on size calculation. The following script runs complete size calculations.

Location: Program Files\Microsoft System Center 2016\DPM\DPM\bin\Manage-DPMDSStorageSizeUpdate.ps1

Script: Manage-DPMDSStorageSizeUpdate.ps1 -ManageStorageInfo [StopSizeAutoUpdate | StartSizeAutoUpdate | GetSizeAutoUpdateStatus | UpdateSizeInfo ] [-UpdateSizeForDS <FilePath>] [-UpdatedDSSizeReport <FilePath>] [-FailedDSSizeUpdateFile <FilePath>]

  • ManageStorageInfo: - Specifies the kind of operation needed.

    • StopSizeAutoUpdate: Stops the size calculations completely. Both UI and PowerShell will not report sizes.

    • StartSizeAutoUpdate: Resumes the size calculations. Immediately after enabling size calculations, use UpdateSizeInfo (in the following options) to recalculate sizes for all the datasources, until which sizes reported in PowerShell and UI may not be correct.

    • GetSizeAutoUpdateStatus: Tells whether size calculations are enabled or disabled.

    • UpdateSizeInfo: Triggers the size calculation and reports the size consumed by datasource. As this can be a long-running operation, use it only when needed, for scenarios such as billing. During this time, backups may fail with vhd mount errors.

  • UpdateSizeForDS: Path to a text file with a list of Datasource IDs for which size needs to be calculated, with a datasourceID on each line. When not passed, size calculation is triggered for all the datasources. Use after using UpdateSizeInfo in ManageStorageInfo. To get the Datasource IDs of specific datasources, use Get-DPMProtectionGroup | Get-DPMDatasource | Format-table -Property Computer,name,ObjectType,Id.

  • UpdatedDSSizeReport: Path to a file that stores the updated datasource sizes. When not passed sizes.csv, a file is created in the execution directory. Use after UpdateSizeInfo in ManageStorageInfo.

  • FailedDSSizeUpdateFile: Path to a file to store the Datasource IDs for the datasources for which the storage consumption couldn’t be calculated. This may happen due to reasons as ongoing backups. When not passed failedDS.txt file is created in the execution directory. This file can be given as input to “UpdateSizeForDS” to update the sizes of all the datasources. This should be used after using UpdateSizeInfo in ManageStorageInfo.

Hyper-V RCT - recover as files for D-T backup fails

Description: Recovery of Hyper-V RCT VMs as files created directly on tape (D-T) fails. D-D-T does not exhibit this issue.

Workaround: Use Alternate Location Recovery as a VM, and then transfer those files to the desired location.

File Server end user recovery (EUR) not available when using Modern Backup Storage (MBS)

Description: If you use Modern Backup Storage (MBS) with DPM 2016, File Server end-user recovery is not available.

Workaround: None. File Server EUR is not supported when using MBS.

DPM 1801 Release notes

The following bugs have been fixed in the DPM 1801 release:

  • Upgrading the DPM agent on the production server causes an unexpected reboot.
  • Consistency checks for Hyper-V VMs transferred more data than the size of the VMs.

The following issues exist in the 1801 release.

Silent Installation of System Center DPM with SQL Server 2008

Description: DPM 2016 RTM won't silently install on SQL Server 2008.

Workaround: Deploy DPM 2016 RTM on a version of SQL Server higher than 2008, or use the DPM 2016 Setup user interface.

Remove-DPMDiskStorage cmdlet might delete volumes with active or inactive backups

Description: If the volume's datasources are being backed up (actively or inactively), when the Remove-DPMDiskStorage cmdlet is used to remove volumes from DPM, the datasources can be removed too.

Workaround: Before using the cmdlet to remove the volumes, make sure the volume's datasources aren't in use (actively or inactively).

DPM 2016 on Windows Server 2016 hangs

Description: Memory consumption on the DPM Server increases continuously until it reaches 90%. Memory consumption slows the DPM server.

Workaround: Upgrade DPM to DPM UR2 and install KB4013429 to fix this issue.

Hyper-V VMs are protected twice on VM upgrade

Description: When upgrading a Hyper-V VM from Windows Server 2012 R2 to Windows Server 2016, two versions of the VM appear in the Create Protection Group Wizard.

Workaround: For the VMs that haven't been upgraded, stop protection with Retain Data. Upgrade the VM, and create a new protection group. Then refresh the data sources, and protect the VMs. When you reapply protection, the VMs are protected using Resilient Change Tracking (RCT).

Agent installation fails on Windows Server 2008, Windows Server 2008 R2

Description: When protecting Windows Server 2008, or Windows Server 2008 R2, installing the agent can fail.

Workaround: Upgrade the Windows Management Framework (WMF) on the production server to 4.0. Download the WMF from Windows Management Frame 5.1(https://www.microsoft.com/download/details.aspx?id=54616). Install WMF and then install the agent.

Restoring a previous version of an upgraded Hyper-V VM causes future recovery points to fail.

Description: If you upgrade a protected 2012 R2 Hyper-V VM to the 2016 version, then stop protecting the VM (but retain data), and then re-enable protection, if you then recover a 2012 R2 copy at the original location, further backups may fail.

Workaround: After recovery, change the VM Version to 2016, then run a Consistency Check.

Bare Metal Recovery protection failures

Description: If you configure Bare Metal Recovery (BMR) protection, the BMR protection job may fail with the message that the replica size is not sufficiently large.

Workaround: Use the following registry path to change the default replica size for BMR data sources. Open the registry editor and increase the replica size for the following key:

HKLM\Software\Microsoft\Microsoft Data Protection Manager\ConfigurationReplicaSizeInGBForSystemProtectionWithBMR (DWORD)

Reprotecting the DPM database after upgrading to DPM 2016

Description: When you upgrade from System Center DPM 2012 R2 to System Center Data Protection Manager 2016, the DPM database name can change in some scenarios.

Workaround: If you are protecting a DPM database, be sure to enable protection for the new DPM database. Once the DPM upgrade is validated, you can remove protection for the old DPM database.

Recovery Points not being pruned, leading to an accumulation of Recovery Points

Description: DPM prunes recovery points older than the retention range. During the pruning process, DPM calculates the storage consumed by those recovery points to be pruned. Storage calculation delays pruning.

Workaround: Configure DPM to skip calculating the size of recovery points to be pruned. As a result, the pruning script runs faster, and prunes all recovery points older than the retention range, relieving any storage pressures. The storage consumed per data source isn't updated until DPM finishes pruning. The storage consumption per volume continues to reflect the correct values. Use a PowerShell script to turn on size calculation. The following script runs complete size calculations.

Location: Program Files\Microsoft System Center 2016\DPM\DPM\bin\Manage-DPMDSStorageSizeUpdate.ps1

Script: Manage-DPMDSStorageSizeUpdate.ps1 -ManageStorageInfo [StopSizeAutoUpdate | StartSizeAutoUpdate | GetSizeAutoUpdateStatus | UpdateSizeInfo ] [-UpdateSizeForDS <FilePath>] [-UpdatedDSSizeReport <FilePath>] [-FailedDSSizeUpdateFile <FilePath>]

  • ManageStorageInfo: - Specifies the kind of operation needed.

    • StopSizeAutoUpdate: Stops the size calculations completely. Both UI and PowerShell will not report sizes.

    • StartSizeAutoUpdate: Resumes the size calculations. Immediately after enabling size calculations, use UpdateSizeInfo (in the following options) to recalculate sizes for all the datasources, until which sizes reported in PowerShell and UI may not be correct.

    • GetSizeAutoUpdateStatus: Tells whether size calculations are enabled or disabled.

    • UpdateSizeInfo: Triggers the size calculation and reports the size consumed by datasource. As this can be a long-running operation, use it only when needed, for scenarios such as billing. During this time, backups may fail with vhd mount errors.

  • UpdateSizeForDS: Path to a text file with a list of Datasource IDs for which size needs to be calculated, with a datasourceID on each line. When not passed, size calculation is triggered for all the datasources. Use after using UpdateSizeInfo in ManageStorageInfo. To get the Datasource IDs of specific datasources, use Get-DPMProtectionGroup | Get-DPMDatasource | Format-table -Property Computer,name,ObjectType,Id.

  • UpdatedDSSizeReport: Path to a file that stores the updated datasource sizes. When not passed sizes.csv, a file is created in the execution directory. Use after UpdateSizeInfo in ManageStorageInfo.

  • FailedDSSizeUpdateFile: Path to a file to store the Datasource IDs for the datasources for which the storage consumption couldn’t be calculated. This may happen due to reasons as ongoing backups. When not passed failedDS.txt file is created in the execution directory. This file can be given as input to “UpdateSizeForDS” to update the sizes of all the datasources. This should be used after using UpdateSizeInfo in ManageStorageInfo.

Hyper-V RCT - recover as files for D-T backup fails

Description: Recovery of Hyper-V RCT VMs as files created directly on tape (D-T) fails. D-D-T backups will not exhibit this issue.

Workaround: Use Alternate Location Recovery as a VM, and then transfer those files to the desired location.

File Server end user recovery (EUR) not available when using Modern Backup Storage (MBS)

Description: If you use Modern Backup Storage (MBS) with DPM 2016, File Server end-user recovery is not available.

Workaround: None. File Server EUR is not supported when using MBS.

Error 4387 might appear while installing DPM

Description: While installing the Data Protection Manager, when you enter an SQL instance in the Data Protection Manager Setup > Prerequisites check> Instance of SQL server text box, error 4387 might appear.

Workaround: Perform the required actions as detailed in this KB article and try the DPM setup again.

System Center DPM 2016 Release Notes

The following sections summarize the release notes for DPM 2016 and include the applicable known issues and workarounds.

Silent Installation of System Center DPM with SQL Server 2008

Description: DPM 2016 RTM won't silently install on SQL Server 2008.

Workaround: Deploy DPM 2016 RTM on a version of SQL Server higher than 2008, or use the DPM 2016 Setup user interface.

Remove-DPMDiskStorage cmdlet might delete volumes with active or inactive backups

Description: If the volume's datasources are being backed up (actively or inactively), when the Remove-DPMDiskStorage cmdlet is used to remove volumes from DPM, the datasources can be removed too.

Workaround: Before using the cmdlet to remove the volumes, make sure the volume's datasources aren't in use (actively or inactively).

DPM 2016 on Windows Server 2016 hangs

Description: Memory consumption on the DPM Server increases continuously until it reaches 90%. Memory consumption slows the DPM server.

Workaround: Upgrade DPM to DPM UR2 and install KB4013429 to fix this issue.

Hyper-V VMs are protected twice on VM upgrade

Description: When upgrading a Hyper-V VM from Windows Server 2012 R2 to Windows Server 2016, two versions of the VM appear in the Create Protection Group Wizard.

Workaround: For the VMs that haven't been upgraded, stop protection with Retain Data. Upgrade the VM, and create a new protection group. Then refresh the data sources, and protect the VMs. When you reapply protection, the VMs are protected using Resilient Change Tracking (RCT).

Agent installation fails on Windows Server 2008, Windows Server 2008 R2

Description: When protecting Windows Server 2008, or Windows Server 2008 R2, installing the agent can fail.

Workaround: Upgrade the Windows Management Framework (WMF) on the production server to 4.0. Download the WMF from Windows Management Frame 5.1(https://www.microsoft.com/download/details.aspx?id=54616). Install WMF and then install the agent.

Restoring a previous version of an upgraded Hyper-V VM causes future recovery points to fail.

Description: If you upgrade a protected 2012 R2 Hyper-V VM to the 2016 version, then stop protecting the VM (but retain data), and then re-enable protection, if you then recover a 2012 R2 copy at the original location, further backups may fail.

Workaround: After recovery, change the VM Version to 2016, then run a Consistency Check.

Bare Metal Recovery protection failures

Description: If you configure Bare Metal Recovery (BMR) protection, the BMR protection job may fail with the message that the replica size is not sufficiently large.

Workaround: Use the following registry path to change the default replica size for BMR data sources. Open the registry editor and increase the replica size for the following key:

HKLM\Software\Microsoft\Microsoft Data Protection Manager\ConfigurationReplicaSizeInGBForSystemProtectionWithBMR (DWORD)

Reprotecting the DPM database after upgrading to DPM 2016

Description: When you upgrade from System Center DPM 2012 R2 to System Center Data Protection Manager 2016, the DPM database name can change in some scenarios.

Workaround: If you are protecting a DPM database, be sure to enable protection for the new DPM database. Once the DPM upgrade is validated, you can remove protection for the old DPM database.

Recovery Points not being pruned, leading to an accumulation of Recovery Points

Description: DPM prunes recovery points older than the retention range. During the pruning process, DPM calculates the storage consumed by those recovery points to be pruned. Storage calculation delays pruning.

Workaround: Configure DPM to skip calculating the size of recovery points to be pruned. As a result, the pruning script runs faster, and prunes all recovery points older than the retention range, relieving any storage pressures. The storage consumed per data source isn't updated until DPM finishes pruning. The storage consumption per volume continues to reflect the correct values. Use a PowerShell script to turn on size calculation. The following script runs complete size calculations.

Location: Program Files\Microsoft System Center 2016\DPM\DPM\bin\Manage-DPMDSStorageSizeUpdate.ps1

Script: Manage-DPMDSStorageSizeUpdate.ps1 -ManageStorageInfo [StopSizeAutoUpdate | StartSizeAutoUpdate | GetSizeAutoUpdateStatus | UpdateSizeInfo ] [-UpdateSizeForDS <FilePath>] [-UpdatedDSSizeReport <FilePath>] [-FailedDSSizeUpdateFile <FilePath>]

  • ManageStorageInfo: - Specifies the kind of operation needed.

    • StopSizeAutoUpdate: Stops the size calculations completely. Both UI and PowerShell will not report sizes.

    • StartSizeAutoUpdate: Resumes the size calculations. Immediately after enabling size calculations, use UpdateSizeInfo (in the following options) to recalculate sizes for all the datasources, until which sizes reported in PowerShell and UI may not be correct.

    • GetSizeAutoUpdateStatus: Tells whether size calculations are enabled or disabled.

    • UpdateSizeInfo: Triggers the size calculation and reports the size consumed by datasource. As this can be a long-running operation, use it only when needed, for scenarios such as billing. During this time, backups may fail with vhd mount errors.

  • UpdateSizeForDS: Path to a text file with a list of Datasource IDs for which size needs to be calculated, with a datasourceID on each line. When not passed, size calculation is triggered for all the datasources. Use after using UpdateSizeInfo in ManageStorageInfo. To get the Datasource IDs of specific datasources, use Get-DPMProtectionGroup | Get-DPMDatasource | Format-table -Property Computer,name,ObjectType,Id.

  • UpdatedDSSizeReport: Path to a file that stores the updated datasource sizes. When not passed sizes.csv, a file is created in the execution directory. Use after UpdateSizeInfo in ManageStorageInfo.

  • FailedDSSizeUpdateFile: Path to a file to store the Datasource IDs for the datasources for which the storage consumption couldn’t be calculated. This may happen due to reasons as ongoing backups. When not passed failedDS.txt file is created in the execution directory. This file can be given as input to “UpdateSizeForDS” to update the sizes of all the datasources. This should be used after using UpdateSizeInfo in ManageStorageInfo.

Hyper-V RCT - recover as files for D-T backup fails

Description: Recovery of Hyper-V RCT VMs as files created directly on tape (D-T) fails. D-D-T backups will not exhibit this issue.

Workaround: Use Alternate Location Recovery as a VM, and then transfer those files to the desired location.

File Server end user recovery (EUR) not available when using Modern Backup Storage (MBS)

Description: If you use Modern Backup Storage (MBS) with DPM 2016, File Server end-user recovery is not available.

Workaround: None. File Server EUR is not supported when using MBS.

Error 4387 might appear while installing DPM

Description: While installing the Data Protection Manager, when you enter an SQL instance in the Data Protection Manager Setup > Prerequisites check> Instance of SQL server text box, error 4387 might appear.

Workaround: Perform the required actions as detailed in this KB article and try the DPM setup again.

Latest report files are not automatically updated

Description: With DPM 2016 UR10, issue with DPM report formatting and volume to volume migration reporting is fixed. However, the existing report files are not automatically replaced with the updated files.

Workaround: Follow these steps to replace the existing report files:

Replace the ReportSRV10.dll

  1. Stop the SQL Server Reporting service

  2. Select the updated ReportSRV10.dll file present in C:\Program Files\Microsoft System Center\DPM\DPM\bin and replace the existing DLL files in the following folder:

    C:\Program Files\Microsoft SQL Server\MSRS13.MSDPM2012\Reporting Services\ReportServer\bin

  3. Start the SQL Server Reporting service.

Replace the RDL files

  1. On DPM, open the SQL Reporting Services portal URL.

  2. On the portal, the DPMReports folder is present in the format DPMReports_<GUID>.

    Reports folder

    Note

    You can see only one folder with this naming convention. If DPM is upgraded from a previous version, the previous folder might still exist, but you can’t open it.

  3. Select and open the DPMReports_<GUID> folder. The individual report files are displayed.

    List of individual report files

  4. Select the report files that don't end with Report, right-click Option, and then select Manage.

    Manage report files

  5. In the new page, select Replace to replace with the latest report files.

    Replace report files

    The latest report files are available in the DPM installation path:

    For example: C:\Program Files\Microsoft System Center\DPM\DPM\bin\DpmReports

  6. After the files are replaced, ensure that the Name and Description are intact and aren't empty.

  7. Restart DPM and use the report files.

Next steps