Release Notes for Data Protection Manager in System Center 2012 R2
Updated: July 20, 2016
Applies To: System Center 2012 R2 Preview, System Center 2012 R2 Data Protection Manager
Before you install and use Data Protection Manager (DPM) in System Center 2012 R2, read these release notes.
In scaled-up environments, the following rules must be disabled if you are not using Reporting: Collect Event Data and Collect DPM Backup Event.
The Scoped Administrator Console will not work on Windows Vista (32-bit).
The Scoped Administrator Console will not start until you open the Operations Manager console at least once.
The DPM database cannot be on a clustered or mirrored instance of Microsoft SQL Server.
If you install a protection agent using the disconnected installation after a connected installation fails, the alerts will continue to appear even though the installation is complete.
You cannot rename a cluster protected by DPM. If the cluster must be renamed, stop protection (with retain protected data option turned on), rename the cluster, and then re-protect the data.
When enabling co-location for two protection groups on a tape, the backup method for both protection groups must be identical.
Databases in SharePoint, protected by the primary DPM server cannot be protected as SQL databases by the secondary DPM server.
Protection agent jobs may fail for SQL Server 2012 databases
Description: DPM recovery, consistency check, or initial replica creation jobs may fail for Microsoft SQL Server 2012 databases, resulting in an "Unable to configure protection" alert. This occurs because the local protection agent does not have administrative (sysadmin) privileges on the SQL Server instance and is thus unable to configure protection.
Workaround: Manually set sysadmin privileges for Microsoft SQL Server 2012 database instances to allow protection jobs to run successfully, as follows:
Using Management Studio, connect to SQL Server 2012, then click and expand Security. Next, click and expand Logins, then right-click NT AUTHORITY\SYSTEM and click Properties. Click Serverroles, then click sysadmin and click OK.
Centralized monitoring of DPM is not supported on Windows Server 2008 R2
Description: The DPM Management Pack for System Center 2012 R2 cannot monitor instances of DPM for System Center 2012 R2 installed on Windows Server 2008 R2.
Workaround: Upgrade the operating system on the DPM server to Windows Server 2012.