Article
09/09/2016

Release Notes for Data Protection Manager in System Center 2012 SP1

Updated: May 13, 2016

Applies To: System Center 2012 R2 Data Protection Manager

These release notes contain information that is required to successfully install Data Protection Manager (DPM) in System Center 2012 Service Pack 1 (SP1). They contain information that is not available in the product documentation.

Before you install and use DPM, read these release notes about DPM. These release notes apply to System Center 2012 SP1.

Known Issues

If you have configured page-file exclusion for your virtual machine protection and it was backed up using saved-state backup, after recovery the virtual machine might generate boot errors when it starts up. In this scenario, the virtual machine reboots automatically.
DPM cannot protect databases that are stored on remote server message block (SMB) shares.
If you are removing the update for Windows Azure Online Backup Agent through Add/Remove Programs, ensure that there are no backup or recovery jobs in progress. A start of the DPM server might be forced because the application was running during the uninstallation procedure.
You cannot restart a failed job for particular data sources within a protection group if you are using a PowerShell script. The cmdlet will rerun the job for all the data sources in the protection group.

Unable to backup virtual machines

Description: Virtual machine enters a paused state or a CSV volume goes offline when you try to create a backup of the virtual machine on a Windows Server 2012-based failover cluster.

Workaround: Install the update KB2813630.

Backups are not progressing

Description: If you are backing up virtual machines on remote SMB, the backups are stuck for a long time with no data transfer.

Workaround: Install the update KB2770917.

DPM cancels all running jobs

Description: If the DPM Administrator Console stops working twice while trying the same jobs and requires a restart, on the third restart DPM cancels all the running jobs. This might cause the replicas to become inconsistent.

Workaround: Run a consistency check to ensure that all the replicas are in a good state.

Backup jobs of virtual machines stop

Description: If the iSCSI target storage provider is enabled on the protected computer, DPM backups of virtual machines that are hosted on Hyper-V clusters may stop.

Workaround: Add the following registry entry to the protected computer:

Warning

Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.

Key	HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Data Protection Manager\Agent\
Value	UseSystemSoftwareProvider
Data
Type	DWORD

Disaster recovery fails

Description: Disaster recovery protection fails with a “Parameter incorrect” message.

Workaround: If you have BitLocker Drive Encryption enabled on a volume that uses Resilient File System (ReFS), turn it off.

SQL Server backups transfer large amounts of data

Description: Express Full backups for Microsoft SQL Server databases transfer large amounts of data (almost the size of the primary .mdf file). This typically happens after you have run DBCC CHECKDB on a Windows Server 2008 server.

Workaround: Install the update KB2471430on the server running SQL Server.

Exchange Server 2013 backups fail

Description: Microsoft Exchange Server 2013 backups fail if the option to run Eseutil on the backup is enabled.

Workaround: Install the VC++ 2012 redistributable on the DPM server.

For more information, see Visual C++ Redistributable for Visual Studio 2012 Update 1.

Reports appear unformatted

Description: Reports are not displaying correctly in Internet Explorer.

Workaround: Turn on Compatibility View in the Address bar in Internet Explorer.

Online backups fail

Description: Online backups will fail for a replica volume that has a drive letter assigned to it.

Workaround: Remove the drive letter for the volume and retry the backup.

Unable to detect Windows Azure Online Backup

Issue: When you uninstall Windows Azure Online Backup Update, DPM does not detect Windows Azure Online Backup.

Workaround: Force DPM to work with the previous version of Windows Azure Online Backup by setting the following registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{8AB21D86-21F0-430A-9AD1-2D90077104C3}\InstallLocation to <Drive>:\Program Files\Windows Azure Online Backup Agent\.