Release Notes for System Center 2012 - Data Protection Manager

Updated: May 13, 2016

Applies To: System Center 2012 R2 Data Protection Manager

These release notes contain information that is required to successfully install System Center 2012 – Data Protection Manager (DPM). 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.

• 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.

Description:  DPM supports the following languages: English, French, German, Spanish, Italian, Japanese, Portuguese (Brazilian), Russian, and Chinese (Simplified, China).

Description:  DPM supports upgrade for DPM 2010 Chinese (Traditional, Taiwan) and Korean to English only.

Description: When you try to configure reporting, if DPM installation fails with the following error message: “The password is shorter than required. (The password could also be too long, be too recent in its change history, not have enough unique characters, or not meet another password policy requirement.”

Workaround: Format the computer, and rerun Setup.

Description:

• The Central Console for DPM supports only System Center 2012 - Operations Manager.

• The Central Console is not supported on a Local Management Group (LMG) topology.

• If the Operations Manager administrator has not been configured for any of the Central Console roles, they will not be able to view any jobs. To view jobs, restart Operations Manager as an administrator and assign DPM tasks to the administrator user role.

• After the Operations Manager Agent is installed on the DPM server, the following registry key settings are recommended so that the data source discoveries can work properly:

  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.

  [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Modules\Global\PowerShell] "ScriptLimit"=dword:0000000f

  Restart the Health Service (display name: System Center Management) after you change the registry settings. This must be repeated on every DPM server that you are monitoring with Operations Manager.

• You cannot restore encrypted files that were protected from an NTFS volume to a Resilient File System (ReFS) volume.

• You cannot protect custom volumes with ReFS.

• You must enable the Data Deduplication role on the DPM server to protect deduplicated volumes.

• If you protect data to tape, the data will be stored in unoptimized form.

• End-user recovery for deduplicated volumes will be done in unoptimized form.

• If the DPM Administrator Console stops working twice while trying the same jobs and must be restarted, on the third restart DPM will cancel all the running jobs. This may cause the replicas to become inconsistent. You must run a consistency check to ensure that all the replicas are in a good state.

• After you uninstall DPM, you must manually disable the deduplication feature in Windows if you do not want to continue using it.

• For Live Migration and DPM Scale-Out deployments, the DPM server, Virtual Machine Manager (VMM) server, and Hyper-V hosts should be in the same domain.

• All components of the virtual machine should be on one file share.

• IPv4 or IPv6 addresses for the storage location file server are not supported.

• Secondary protection is not available for virtual machine mobility, scale-out, and deduplicated volumes.

• Ensure that all Hyper-V hosts and virtual machines are discovered by the VMM server before you begin creating protection groups.

• If you configure page-file exclusion for your virtual machine protection and it was backed up using saved-state backup, after recovery the virtual machine might encounter errors when it starts up. In this scenario, the virtual machine restarts automatically.

• If iSCSI target storage provider is enabled on the protected computer, DPM backups of virtual machines that are hosted on Hyper-V clusters might stop. Add the following registry entry to solve this problem.

  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

• Do the following to protect the Microsoft SQL Server 2012 database:

  Connect to the SQL Server 2012 instance through the Management Studio, and then select and expand Security. Select and expand Logins, right-click NT AUTHORITY\SYSTEM, and then click Properties. Click Serverroles, click sysadmin, and then click OK.

• DPM cannot protect databases that are stored on remote Server Message Block (SMB) shares.

• When DPM is protecting databases that use the AlwaysOn feature, recovery to the original location is not supported.

• If you have BitLocker Drive Encryption enabled on a volume using Resilient File System (ReFS), disaster recovery protection fails and the “Parameter incorrect” message appears.

• DPM servers with case-sensitive names are not supported.

• Windows Azure Online Backup cannot be monitored using the Central Console.

• Stop protection with online data retention is not supported. When you stop protection for a protection group or data source, its online data is deleted.

• You cannot protect data from a secondary DPM server.

• If your proxy settings are not set by your system administrator, you cannot use the Registration Wizard to set the proxy settings in System Center 2012 SP1 Beta. You must set them manually by using PsExec, which you can download from PsExec v1.98.

  1. Run the following command from an elevated command prompt:

     psexec -i -s “C:\Program Files\Internet Explorer\iexplore.exe”

     Internet Explorer opens.

  2. Click Tools, click Internet Options, click Connections, click LAN settings, clear the Automatically detect setting check box, and then enter the proxy settings.

  3. Close Internet Explorer.

• DPM servers with case-sensitive names are not supported.

• Windows Azure Online Backup cannot be monitored using the Central Console.

• Stop protection with online data retention is not supported. When you stop protection for a protection group or data source, its online data is deleted.

• You cannot protect data from a secondary DPM server.

Release Notes: System Center 2012 - Data Protection Manager