Update Rollup 6 for System Center 2012 R2 Data Protection Manager

Introduction

This article describes the issues that are fixed in Update Rollup 6 for Microsoft System Center 2012 R2 Data Protection Manager. Additionally, this article contains the installation instructions for Update Rollup 6 for System Center 2012 R2 Data Protection Manager.

Notes
  • You have to restart the protected computer after you apply the Data Protection Manager Agent update for Update Rollup 6. Some backup jobs might fail if you don’t restart the protected computer.
  • Existing Data Protection Manager to Windows Azure customers should upgrade to the latest agent (version 2.0.8693.0 or a later version). If the latest agent is not installed, online backups will fail, and no Data Protection Manager to Windows Azure operation will work.

Features that are implemented in this update rollup

  • Option to keep online backup data while deleting a protection group

    When you delete a protection group (PG), you now have a choice of keeping the backup data in Azure or on a local disk. You can always browse the retained data, together with other recovery points, from the server on the Recovery tab. To delete a protection group, follow these steps:
    1. When you delete a PG, you are presented with the option of Delete Storage Online, as you see in the following screen shot:

      Delete Storage Online
    2. Click to clear the option if you want to keep the online backups in Azure.
    3. For recovering the online backup data from Azure, locate the Recovery tab, and then select the production server for which online backups are to be retained.
    4. Select the recovery point to recover the data.

  • Support for SQL Server 2014 as DPMDB

    DPM 2012 R2 Update Rollup 4 added support for protecting SQL Server 2014 as a workload. With this release, you can now use SQL Server 2014 as a DPM configuration database so that you can host your DPM 2012 R2 Update Rollup 6 servers on SQL Server 2014.

    Because the support for SQL Server 2014 as a DPM database is added in Update Rollup 6, the release version of DPM 2012 R2 will not install on SQL Server 2014. To upgrade to SQL Server 2014, follow these steps:
    1. Install the release version of DPM 2012 R2 on SQL Server 2012.
    2. Upgrade DPM to Update Rollup 6.
    3. Upgrade SQL Server to SQL Server 2014.
  • Protection of System State and BMR workloads to Microsoft Azure through Data Protection Manager

    With Update Rollup 6 for System Center 2012 R2 Data Protection Manager, Data Protection Manager can now protect System State and BMR workloads to Microsoft Azure. The online protection option will be enabled for these workloads after you apply this update.

Issues that are fixed in this update rollup

  • Issue 1

    The DPMAM service and the DPMWriter service do not start and stop in default time during DPM Update Rollup installations. This causes installation failures.

  • Issue 2

    The DPMRA service may crash intermittently when it is protecting lots of virtual machines (VMs) in clusters that have high cluster traffic.

  • Issue 3

    The DPM service stops unexpectedly when you try to disable and then re-enable online protection for a workload.

  • Issue 4

    The Attach-ProductionServer.ps1 cmdlet is improved to enable it to attach a primary DPM to a secondary DPM server in Disaster Recovery (DPM-DR) scenarios.

    The command syntax is as follows:

    Attach-ProductionServer.ps1 -DPMServername [Secondary DPM] -PSName [Primary DPM] -Username [PS admin username] -Password [Password] -domain [User domain]


  • Issue 5

    If users have Group Policy enabled during DPM Update Rollup installation, they may sometimes receive the following error message:

    Microsoft System Center 2012 R2 Data Protection Manager Update failed.

    However, the updates are installed successfully.

  • Issue 6

    When you receive a popup error message in DPM that contains a More Information redirection link, the link does not correctly redirect. This causes a "Page Not Found" error.

  • Issue 7

    If you protect System State or BMR after you upgrade to DPM Update Rollup 5, the console may crash or become unresponsive while it is running DPM Inquiry. The fix for this issue was released in update 3040326 and is also included in this update.

  • Issue 8

    The DPM service may crash when an encrypted backup to tape is performed by using FIPS encryption.

  • Issue 9

    The Refresh button in the Create/Modify PG wizard may be disabled even after you select a PS computer.

  • Issue 10

    Policy inconsistency alerts cannot be resolved after you apply the recommended action.

  • Issue 11

    For a Windows 2012 R2 failover cluster that has dedup volumes, DPM may in some cases perform an unoptimized backup.

  • Issue 12

    Create\Modify\Delete on a PG with Clustered File Server data sources may fail with Error 197 or cause a console crash. This specifically occurs after DPM Update Rollup 5 is installed.

  • Issue 13

    You cannot change the Azure backup schedule for an existing PG when you have online backup enabled.

  • Issue 14

    When you expand a cluster host in the protection wizard, the DPM UI may crash.

  • Issue 15

    In some locales, the Refresh button and the surrounding text are not visible in the protection wizard.


How to obtain and install Update Rollup 6 for System Center 2012 R2 Data Protection Manager

Download information

Update packages for Data Protection Manager are available from Microsoft Update or by manual download.

Microsoft Update
To obtain and install an update package from Microsoft Update, follow these steps on a computer that has a Data Protection Manager component installed:
  1. Click Start, and then click Control Panel.
  2. In Control Panel, double-click Windows Update.
  3. In the Windows Update window, click Check Online for updates from Microsoft Update.
  4. Click Important updates are available.
  5. Select the Update Rollup package, and then click OK.
  6. Click Install updates to install the update package.
Manual download of the update packages
To manually download the update packages from the Microsoft Update Catalog, go to the following website:


Installation instructions
Files that are updated in this update rollup
Properties

Article ID: 3030574 - Last Review: May 19, 2015 - Revision: 1

Feedback