Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Update Rollup 10 for System Center 2012 R2 Data Protection Manager

Update Rollup 10 for System Center 2012 R2 Data Protection Manager

View products that this article applies to.

Introduction

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

Note Existing Data Protection Manager to Windows Azure customers should upgrade to the latest agent (2.0.8719.0 or a later version). If this agent is not installed, online backups fail and no Data Protection Manager to Windows Azure operation works.

↑ Back to the top

Issues that are fixed in this update rollup

  • If you try to exclude a page file for a VM running on Microsoft Hyper-V Server 2012 R2 server, DPM may still continue to back up the page file.

  • DPM provides an Active Directory schema extension tool to make required changes to Active Directory for DPM End-User Recovery. However, you may the tool may not work on System Center 2012 R2 Data Protection Manager.

  • If you try to protect a SharePoint content database that has Always On enabled, and there is a failover of the database, you may notice that new sites, lists, and items are not displayed on the Recovery tab. This applies only to new items that are created after failover. Additionally, the issue is automatically resolved after failback.

  • If you run Update Rollup 7 for System Center 2012 R2 Data Protection Manager, or a later version, and then try to do item level recovery for a Hyper-V VM, you may receive the following error message when you click the VHDX file on the Recovery tab:
    DPM Cannot browse the contents of the virtual machine on the protected computer DPMServerName.

  • The DPM Console crashes when you try to open any of the six built-in DPM reports.

  • Optimized item level recovery doesn't work for a SharePoint farm. This causes the full farm data to be copied to the staging server that's running Microsoft SQL Server.

  • The DPM UI crashes when you try to recover online recovery points by using another DPM server that is registered to the same backup vault as the original server.

  • The Get-DPMJob cmdlet does not provide any information about recovery jobs that are performed through the external DPM server.

  • This update revises the message of error code 33504 to add details about the issue and steps to resolve the issue.

  • If you try to protect Microsoft Exchange Server 2016 while you create a protection group, the server that's running Exchange Server is displayed as "Exchange 2013 Database" instead of "Exchange 2016 Database."

  • If you use the DPM Central console, and you receive an EvalShareInquiryAlert (3123) alert on DPM, the alert is still displayed as active in System Center Operations Manager even though the issue is resolved on DPM.

  • DPM crashes when you try to configure SMTP settings.

  • If you try to stop protection of a data source in which the FQDN contains more than 64 characters, the DPM service crashes.

↑ Back to the top


How to obtain and install Update Rollup 10 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
Go to the following website to manually download the update package from the Microsoft Update Catalog:

Download Download the Data Protection Manager update package now.

↑ Back to the top

Installation instructions
To install this update for Data Protection Manager, follow these steps:

  1. Before you install this update, make a backup of the Data Protection Manager database.
  2. Install this rollup package on the server that is running System Center 2012 R2 Data Protection Manager. To do this, run Microsoft Update on the server.
  3. In the Data Protection Manager Administrator Console, update the protection agents. To do this, use one of the following methods.

    Note This Update Rollup agent update requires you to restart protected servers in order to create or change protection groups.

    Method 1: Update the protection agents from the Data Protection Manager Administrator Console
    1. Open the Data Protection Manager Administrator Console.
    2. Click the Management tab, and then click the Agents tab.
    3. In the Protected Computer list, select a computer, and then click Update on the Action pane.
    4. Click Yes, and then click Update Agents.


    Method 2: Update the protection agents on the protected servers
    1. Obtain the update protection agent package from the following directory on the System Center 2012 R2 Data Protection Manager server:

      Data_Protection_Manager_installation_location\DPM\DPM\Agents\RA\4.2.1473.0


      The installation packages are as follows:

      • For x86-based updates: i386\1033\DPMProtectionAgent_KB3143871.msp
      • For x64-based updates: amd64\1033\DPMProtectionAgent_KB3143871_AMD64.msp


    2. Run the appropriate DPMProtectionAgent.msp package on each protected server, based on the architecture of the agent.
    3. Open the Data Protection Manager Administrator Console on the System Center 2012 R2 Data Protection Manager server.
    4. Click the Management tab, and then click the Agents tab. Select the protected server, update the information, and then verify that the agent version number is 4.2.1473.0.

↑ Back to the top

Keywords: kbqfe, kbsurveynew, kbnotautohotfix, kbfix, kbexpertiseinter, atdownload, kb

↑ Back to the top

Article Info
Article ID : 3143871
Revision : 1
Created on : 1/7/2017
Published on : 5/24/2016
Exists online : False
Views : 430