Export (0) Print
Expand All

Update rollups for System Center 2012 R2 - DPM

 

Published: July 29, 2015

Updated: July 29, 2015

This update rollup fix includes:

  • Bugs listed in KB 3065246.

  • Increased support for DPM backup to Azure. We’ve added:

    • The ability to recover data to any DPM server that's registered in an Azure Backup vault. If two or more servers are registered in a vault and back up data to Azure then any of those registered DPM servers can recover data from the vault. To use this feature after installing Update 7 you can enable the setting Add External DPM on the Recovery tab in the DPM console. Specify vault credentials. note that credentials are only valid for two days. If they've expired you'll need to download new credentials from the vault. Select the DPM server whose data needs to be recovered, and provide the encryption password. You can close the dialog after the server appears. Then you can recover the data by browsing the recovery points. To return to the local DPM data view click Clear external DPM.

      Note that if you want to use this feature for existing backed up DPM you'll need to wait at least a day to obtain the DPM protection group related metadata for upload to Azure (this occurs for the first time during the nightly job).

  • Support for protection and backup of data on client computers running Windows 10. You back up in the same way you did with client computers running earlier versions of Windows.

This update is available through Microsoft Update or by manual download. You can download the package and find installation instructions and information about agent updates in KB 3065246.

This update rollup fix includes:

  • Bugs listed in KB 3030574.

  • Support for using SQL Server 2014 as the DPM database. Support for protecting SQL Server 2012 was introduced in Update 4. Now, in Update 6 you can configure a SQL Server running SQL 2012 as your database. You'll need to install Update 6 and then configure DPM to use SQL Server 2014.

  • If you're backing up DPM to Azure you can now select to keep online backed up data when deleting a protection group. When you delete a protection group you can choose whether to preserve backed up 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.

This update is available through Microsoft Update or by manual download. You can download the package and find installation instructions and information about agent updates in KB 3030574.

This update rollup fix includes:

  • Bugs listed in KB 3021791.

  • Ability to protect SharePoint with SQL Server Always On—From Update rollup 5 onwards DPM can protection SharePoint farm SQL Server databases that have Always On enabled.

  • Increased support for DPM backup to Azure. We’ve added:

    • The ability to enable online backup for additional data that’s protected by DPM, including support for backing up protected client computer file data, and SharePoint and Exchange workloads. For more details see Prerequisites for DPM backup to Azure.

    • Support to add multiple retention ranges to specify how long backed up DPM data can be stored in Azure— When you’re backing up DPM-protected data with Azure Backup, you can now configure multiple backup scheduling options and granular retention ranges for the data. This enables you to store data in Azure for long periods (up to years), providing an alternative to long-term tape storage. For details see Back up DPM workloads with Azure Backup.

    • Support to perform offline initial replication of DPM data stored in Azure using the Azure Import feature— If you enable online backup for DPM protection groups that contain large amounts of data, from Update Rollup 5 onwards you can select to do initial replication of the data offline using the Azure Import tool. You copy the data to a hard drive and then send that drive to a Microsoft datacenter where it’s uploaded to your Azure storage account. Read more in Set up DPM to back up to Azure.

  • Support for running DPM as a Windows virtual machine in VMWare to protect supported workloads that are also running as VMWare virtual machines. For details of supported workloads see the DPM protection support matrix.

  • In DPM monitoring a new SLA alerts job keeps you up-to-date if backup and scheduling service-level agreements (SLAs) aren’t on track. At 12.00 AM on a daily basis the Missed SLA Alerts job runs and collects information for the previous day. For example if you configure a backup every day to run every 8 hours and none of the backups run as expected, three Missed SLA alerts will be issued for that day.

  • A new Operations Manager Management Pack and updated versions of existing Management Packs—This update provides a new DPM Reporting Management Pack. This pack provides a number of predefined views that report on DPM disk and tape management and utilization, performance of backup SLAs, and backup and recovery jobs. Alternatively you can generate reports based on custom queries and views. For an overview see Monitor DPM with Operations Manager. More detailed documentation is available when you download the management pack.

This update is available through Microsoft Update or by manual download. You can download the package and find installation instructions and information about agent updates in KB 3021791.

This update rollup fix includes:

  • Bugs listed in KB 3009516

  • Ability to protect SQL Server 2012 SP2 and SQL Server 2014.

  • Ability to run SQL Server 2012 SP2 as the DPM database.

  • Simplified registration process when running DPM with Azure Backup. For details see Configure Azure backup for DPM data.

This update is available through Microsoft Update or by manual download You can download the package and find installation instructions in KB 3009516.

This update rollup fix includes:

This update is available through Microsoft Update or by manual download You can download the package and find installation instructions in KB 2966014.

Update rollup 3 scales backups for Hyper-V virtual machines using Cluster Shared Volume (CSV) storage and scale-out file server storage. You can run a backup of up to 512 virtual machines on a single DPM server once a day with an SLA of at least 95%.

In order to use this feature you’ll need to install KB 2919355 on the Hyper-V host server. If you’re running Hyper-V in a cluster:

  • Upgrade the DPM agent to the latest version for DPM 2012 R2 Update Rollup 3 on all nodes of the cluster

  • Install KB 2919355 on each cluster node. You’ll need to restart the node after the installation.

When you scale up backup of virtual machines you need to be able to isolate backup and production windows to make best use of resources. Update rollup 3 allows you to create protection and synchronization windows for virtual machines only. You can create specific time windows that restrict start and finish times for backups and consistency checks. Pending unscheduled jobs outside the window will be cancelled, and in-progress jobs will be allowed to continue. For instructions see Configure backup windows for virtual machines.

Update rollup 3 introduces a certification process for 3rd party tape devices over synthetic fiber channel-to-tape. This process is similar to the existing tape certification process for DPM.

This update rollup includes:

  • Bug fixes listed in KB 2958100.

  • Support for protecting servers running Windows Server 2003.

  • Support for SQL Server 2012 databases deployed in a cluster that are configured to use AlwaysOn availability groups.

  • After installing the protection agent on servers running Windows Server 2003 you might need to perform an agent refresh on the DPM server.

  • If you run the Uninstall Agents wizard to stop protection of a Windows Server 2003 server that is online, the wizard will fail with error 33241: “Microsoft .NET Framework 4 not installed on this computer”. If this occurs do either of the following:

    • On the protected server manually uninstall the DPM agent using Add/Remove Programs. Then on the DPM server open an elevated command prompt, navigate to C:\Program Files\Microsoft Data Protection Manager\DPM\bin, and run command: Remove-protectionserver.ps1. Specify the FQDN of the protected server to remove the agent.

    • Alternatively, manually uninstall the DPM agent on the protected server, shutdown the Windows Server 2003 server or remove it from the network, then run the Unstall Agent wizard and select to remove the DPM record from the DPM database.

  • You’ll need to restart the DPM server after installing the update.

After you install the update rollup you’ll need to complete a few steps to start protecting servers running Windows Server 2003:

  1. Install the DPM protection agent on the Windows Server 2003 server. The installer is located on the DPM server as follows:

    • 64-bit agent—<DPMInstallationLocation>\DPM\agents\RA\4.2.1224.0\amd64\1033\DPMAgentInstaller_Win2K3_AMD64.exe

    • 32-bit agent—<DPMInstallationLocation>\DPM\agents\RA\4.2.1224.0\i386\1033\DPMAgentInstaller_Win2K3_i386.exe

  2. Open an elevated command prompt and navigate to location: C:\Program Files\Microsoft Data Protection Manager\DPM\bin.

  3. Run the command: SetDpmServer.exe –dpmservername [DPM_SERVERNAME]

  4. Attach the protection agent running on the Windows Server 2003 server to the DPM server using either of the following methods:

    • Run the Protection Agent Installation Wizard. On the Select Agent Deployment Method page select Attach Agents, and in the Select Computers page select the Windows Server 2003 server.

    • Alternatively, run this Windows PowerShell script on the DPM server: .\Attach-ProductionServer.ps1 <DPMServerName> <Production Server Name> <User Name> <Password> <Domain>. A password isn’t required.

As an alternative you can perform steps 1 to 3 with a silent install at an elevated command prompt: [Installer].exe /q [DPM_SERVERNAME] /IAcceptEULA. [DPM_SERVERNAME] is optional.

This update rollup includes fixes for:

  • Error 0x80070057—This error occurs when a session is closed prematurely and is caused by a consistency check failure.

  • Slow SQL Server performance—This issue occurs when lots of concurrent calls to the SQL Server from the DPM console cause slow SQL Server performance. The DPM console runs out of connection and might hang or crash.

  • DPM console crash with error “Paths that begin with \\?\GlobalRoot are internal to the kernel and should not be opened by managed applications.

You can get update rollup 1 in Microsoft KB 2904687.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft