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.

Description of Update Rollup 2 for System Center 2012 R2 Data Protection Manager


View products that this article applies to.

This update rollup was re-released on May 20, 2014 to resolve a "DPMAMService" crash that occurred if the original update (KB 2958100) was applied.

If you already installed Update Rollup 2 on your Windows Server 2003 servers, you do not have to reinstall the Update Rollup 2 agent that is required for Windows Server 2003 communication for this re-release. Additional updates after this re-release will install and work as expected.

↑ Back to the top


Introduction

This article describes the new features and the issues that are fixed in Update Rollup 2 for Microsoft System Center 2012 R2 Data Protection Manager (DPM). This article also contains installation instructions for Update Rollup 2 for System Center 2012 R2 Data Protection Manager, and it contains agent installation instructions to protect Windows Server 2003 workloads.

↑ Back to the top


New features in this update rollup

  • Support for Windows Server 2003 workloads

    DPM 2012 R2 now supports backup and recovery of Windows Server 2008 and Windows Server 2003 servers. After you install Update Rollup 2, you will be able to protect Windows Server 2008 and Windows Server 2003 by using DPM 2012 R2. The following workloads are supported in Windows Server 2008 and Windows Server 2003:
    • Microsoft SQL Server 2008 R2, Microsoft SQL Server 2008, Microsoft SQL Server 2005
    • Microsoft Office SharePoint Server 2007
    This update includes a new agent for Windows Server 2003. If you have not previously installed Update Rollup 2, see the "Installation instructions" section.
  • Protection of SQL AlwaysOn with Clustering

    Protection and recovery of availability groups that are built with or without clustered instances is now supported and works seamlessly in the same manner that it does for nonclustered availability groups.

    Primary/Secondary ClusteredStand-alone
    ClusteredSupported in UR2Supported in UR2
    Stand-aloneSupported in UR2Already supported

Issues that are fixed in this update rollup

This update fixes the following issues that were not previously documented in the Microsoft Knowledge Base:
  • Catalog generation fails for SharePoint 2013 sites that contain app store parts.
  • DPM does not display recovery point volume used space information. The value is always set to 0 KB.
  • If the SetBackupComplete command is called prematurely, this causes SetBackupSucceeded to be called and generate a 0x80042301 error in VSS.
  • SharePoint item level recovery fails when the first part of the site URL matches another site in SharePoint.
  • Status reports indicate that the Data Protection Manager data (DPMDB) is not protected even though it is actually protected and valid Recovery Points are recorded for it.
  • An Invalid Trace Message format string causes a second-chance System.FormatException exception and also causes termination of the DPM process.

↑ Back to the top


Installation instructions

To install the update for Data Protection Manager, follow these steps:
 
  1. Before you install this update, make a backup of the DPMDB.
  2. Install the rollup package on the server that is running System Center 2012 R2 Data Protection Manager. To do this, run Microsoft Update on the server.

    Note Before you install this update through Microsoft Update, the Data Protection Manager console should be closed. You may have to restart the Data Protection Manager server after you install this rollup package.
  3. In the Data Protection Manager Administrator console, update the protection agents. To do this, use one of the following methods.
     

    Update the protection agents on Windows Server 2003 servers

    Install the Windows Server 2003 agent by using the following steps in order to protect Windows Server 2003 servers with DPM 2012 R2 UR2:
    1. Install the Microsoft Visual C++ 2008 Redistributable on Windows Server 2003 servers, if it is not already installed.

      Note You receive the following error message if the C++ redistributable is not installed:
       
      Data Protection Manager Setup

      Could not load the setup launch screen. Please contact Microsoft Product Support.
    2. Copy the Windows Server 2003 Agent installer from the DPM server to the Windows Server 2003 server, and then install the agent.
       
      • 64-bit: DPM_Installation_Location\DPM\agents\RA\4.2.1235.0\amd64\1033\DPMAgentInstaller_Win2K3_AMD64.exe
      • 32-bit: DPM_Installation_Location\DPM\agents\RA\4.2.1235.0\i386\1033\
        DPMAgentInstaller_Win2K3_i386.exe
    3. Run the following command at an administrative command prompt:
       
      cd DPM Agent Installation Location\DPM\bin setdpmserver.exe –dpmservername  DPM_Server_Name 
    4. Run the following Windows PowerShell cmdlet to establish a connection with the DPM server:
       
      Attach-ProductionServer.ps1  DPMServerName ProductionServerName UserName Password Domain 
    5. On the DPM server, click Refresh two times on the agent that is connected to the management user interface. Then, validate that the Health Service state is initialized.

    Update the protection agents on other production servers

    To update the protection agents on other production servers, use either of the following methods.
     
    Method 1: Update the protection agents from the Data Protection Manager Administrator
    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 in the Action pane.
    4. Click Yes, and then click Update Agents.

      Note You may have to restart the computer after you install the agent upgrades.
       
    Method 2: Update the protection agents on the protected computers
     
    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.1235.0
      The installation packages are as follows:
       
      • For x86-based updates: i386\1033\DPMAgentInstaller_KB 2963543.exe
      • For x64-based updates: amd64\1033\DPMAgentInstaller_KB 2963543_AMD64.exe
    2. Run the appropriate DPMAgentInstaller.exe package on each protected computer, 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 computers, update the information, and then verify that the agent version number is 4.2.1235.0.
Learn about Installing Protection Agents Manually.
 

Download instructions

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 an applicable System Center 2012 R2 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 packages that you want to install, and then click OK.
  6. To install the selected update packages, click Install updates.

Microsoft Update Catalog

Go to the following website to manually download the update packages from the Microsoft Update Catalog:
 
File information

File Name File Size
(in KB)
File Version
bin\1033\Utils.dll 1,198 4.2.1235.0
bin\1033\Microsoft.EnterpriseStorage.Dls.Prm.dll 2,444 4.2.1235.0
bin\CPWrapper.dll 1,074 4.2.1235.0
bin\VssRequestorWin8.dll 342 4.2.1235.0
bin\DPMRA.exe 5,519 4.2.1235.0
bin\DPMac.exe 1,823 4.2.1235.0
bin\installagentpatch.exe 99 4.2.1235.0
bin\AgentPatchSetup.exe 22 4.2.1235.0
bin\launchpatch.exe 24 4.2.1235.0
bin\1033\inspect.dll 162 4.2.1235.0
bin\patchca.dll 26 4.2.1235.0
bin\DsmFS.dll 913 4.2.1235.0
bin\1033\ObjectModel.dll 1,207 4.2.1235.0
bin\1033\Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.SQL.dll 51 4.2.1235.0
bin\1033\setupUtilv2.dll 603 4.2.1235.0
bin\1028\setuputilv2.dll 603 4.2.1235.0
bin\1029\setuputilv2.dll 603 4.2.1235.0
bin\1031\setuputilv2.dll 603 4.2.1235.0
bin\1036\setuputilv2.dll 603 4.2.1235.0
bin\1038\setuputilv2.dll 603 4.2.1235.0
bin\1040\setuputilv2.dll 603 4.2.1235.0
bin\1041\setuputilv2.dll 603 4.2.1235.0
bin\1042\setuputilv2.dll 603 4.2.1235.0
bin\1043\setuputilv2.dll 603 4.2.1235.0
bin\1045\setuputilv2.dll 603 4.2.1235.0
bin\1046\setuputilv2.dll 603 4.2.1235.0
bin\1049\setuputilv2.dll 603 4.2.1235.0
bin\1053\setuputilv2.dll 603 4.2.1235.0
bin\1055\setuputilv2.dll 603 4.2.1235.0
bin\2052\setuputilv2.dll 603 4.2.1235.0
bin\2070\setuputilv2.dll 603 4.2.1235.0
bin\3076\setuputilv2.dll 603 4.2.1235.0
bin\3082\setuputilv2.dll 603 4.2.1235.0
bin\ClusterInquiry.dll 173 4.2.1235.0
bin\ClusterInquiryLH.dll 195 4.2.1235.0
bin\VssRequestor.dll 340 4.2.1235.0
bin\VssRequestorXP.dll 314 4.2.1235.0
bin\DpmWriterHelperPlugin.dll 514 4.2.1235.0
bin\ExchangeWriterHelperPlugin.dll 802 4.2.1235.0
bin\FileWriterHelperPlugin.dll 583 4.2.1235.0
bin\GenericDatasourceWriterHelperPlugin.dll 748 4.2.1235.0
bin\GenericNonVssDatasourceHelperPlugin.dll 701 4.2.1235.0
bin\SpSearchWriterHelperPlugin.dll 602 4.2.1235.0
bin\SQLWriterHelperPlugin.dll 959 4.2.1235.0
bin\WSSWriterHelperPlugin.dll 768 4.2.1235.0
bin\HypervVhdHelper.dll 82 4.2.1235.0
bin\DpmoVhdManager.dll 94 4.2.1235.0
bin\hypervVhdManager.dll 133 4.2.1235.0
bin\WSSCmdletsWrapper.exe 199 4.2.1235.0
bin\DPMClientService.exe 526 4.2.1235.0
bin\DPMLA.exe 2,478 4.2.1235.0
bin\Microsoft.EnterpriseStorage.Dls.Prm.MbcParser.dll 448 4.2.1235.0
bin\1033\dpmbackup.exe 361 4.2.1235.0
bin\1028\dpmbackup.exe 359 4.2.1235.0
bin\1029\dpmbackup.exe 362 4.2.1235.0
bin\1031\dpmbackup.exe 363 4.2.1235.0
bin\1036\dpmbackup.exe 362 4.2.1235.0
bin\1038\dpmbackup.exe 363 4.2.1235.0
bin\1040\dpmbackup.exe 362 4.2.1235.0
bin\1041\dpmbackup.exe 360 4.2.1235.0
bin\1042\dpmbackup.exe 360 4.2.1235.0
bin\1043\dpmbackup.exe 362 4.2.1235.0
bin\1045\dpmbackup.exe 363 4.2.1235.0
bin\1046\dpmbackup.exe 362 4.2.1235.0
bin\1049\dpmbackup.exe 362 4.2.1235.0
bin\1053\dpmbackup.exe 362 4.2.1235.0
bin\1055\dpmbackup.exe 362 4.2.1235.0
bin\2052\dpmbackup.exe 359 4.2.1235.0
bin\2070\dpmbackup.exe 363 4.2.1235.0
bin\3076\dpmbackup.exe 359 4.2.1235.0
bin\3082\dpmbackup.exe 363 4.2.1235.0
bin\1033\dpmwriter.exe 606 4.2.1235.0
bin\1028\dpmwriter.exe 606 4.2.1235.0
bin\1029\dpmwriter.exe 606 4.2.1235.0
bin\1031\dpmwriter.exe 606 4.2.1235.0
bin\1036\dpmwriter.exe 606 4.2.1235.0
bin\1038\dpmwriter.exe 606 4.2.1235.0
bin\1040\dpmwriter.exe 606 4.2.1235.0
bin\1041\dpmwriter.exe 606 4.2.1235.0
bin\1042\dpmwriter.exe 606 4.2.1235.0
bin\1043\dpmwriter.exe 606 4.2.1235.0
bin\1045\dpmwriter.exe 606 4.2.1235.0
bin\1046\dpmwriter.exe 606 4.2.1235.0
bin\1049\dpmwriter.exe 606 4.2.1235.0
bin\1053\dpmwriter.exe 606 4.2.1235.0
bin\1055\dpmwriter.exe 606 4.2.1235.0
bin\2052\dpmwriter.exe 606 4.2.1235.0
bin\2070\dpmwriter.exe 606 4.2.1235.0
bin\3076\dpmwriter.exe 606 4.2.1235.0
bin\3082\dpmwriter.exe 606 4.2.1235.0
bin\1033\FSPathMerge.exe 302 4.2.1235.0
bin\1028\FSPathMerge.exe 302 4.2.1235.0
bin\1029\FSPathMerge.exe 302 4.2.1235.0
bin\1031\FSPathMerge.exe 302 4.2.1235.0
bin\1036\FSPathMerge.exe 302 4.2.1235.0
bin\1038\FSPathMerge.exe 302 4.2.1235.0
bin\1040\FSPathMerge.exe 302 4.2.1235.0
bin\1041\FSPathMerge.exe 302 4.2.1235.0
bin\1042\FSPathMerge.exe 302 4.2.1235.0
bin\1043\FSPathMerge.exe 302 4.2.1235.0
bin\1045\FSPathMerge.exe 302 4.2.1235.0
bin\1046\FSPathMerge.exe 302 4.2.1235.0
bin\1049\FSPathMerge.exe 302 4.2.1235.0
bin\1053\FSPathMerge.exe 302 4.2.1235.0
bin\1055\FSPathMerge.exe 302 4.2.1235.0
bin\2052\FSPathMerge.exe 302 4.2.1235.0
bin\2070\FSPathMerge.exe 302 4.2.1235.0
bin\3076\FSPathMerge.exe 302 4.2.1235.0
bin\3082\FSPathMerge.exe 302 4.2.1235.0
bin\AgentProxy.dll 224 4.2.1235.0
bin\acreg.dll 262 4.2.1235.0
bin\SetDpmServer.exe 119 4.2.1235.0
bin\DPMFSFilterWrapperDLL.dll 150 4.2.1235.0
bin\TriggerClientJob.dll 46 4.2.1235.0
bin\setagentcfg.exe 142 4.2.1235.0
bin\setupDpmfltr.dll 113 4.2.1235.0
bin\TERuntime.dll 109 4.2.1235.0
bin\EngineUICommon.dll 506 4.2.1235.0
bin\AutoHeal.dll 61 4.2.1235.0
bin\1033\ObjectModelCmdlet.dll 384 4.2.1235.0
bin\1028\zh-TW\ObjectModelCmdlet.resources.dll 30 4.2.1235.0
bin\1029\cs-CZ\ObjectModelCmdlet.resources.dll 32 4.2.1235.0
bin\1031\de-DE\ObjectModelCmdlet.resources.dll 34 4.2.1235.0
bin\1036\fr-FR\ObjectModelCmdlet.resources.dll 34 4.2.1235.0
bin\1038\hu-HU\ObjectModelCmdlet.resources.dll 34 4.2.1235.0
bin\1040\it-IT\ObjectModelCmdlet.resources.dll 33 4.2.1235.0
bin\1041\ja-JP\ObjectModelCmdlet.resources.dll 35 4.2.1235.0
bin\1042\ko-KR\ObjectModelCmdlet.resources.dll 34 4.2.1235.0
bin\1043\nl-NL\ObjectModelCmdlet.resources.dll 32 4.2.1235.0
bin\1045\pl-PL\ObjectModelCmdlet.resources.dll 33 4.2.1235.0
bin\1046\pt-BR\ObjectModelCmdlet.resources.dll 33 4.2.1235.0
bin\1049\ru-RU\ObjectModelCmdlet.resources.dll 40 4.2.1235.0
bin\1053\sv-SE\ObjectModelCmdlet.resources.dll 32 4.2.1235.0
bin\1055\tr-TR\ObjectModelCmdlet.resources.dll 32 4.2.1235.0
bin\2052\zh-CN\ObjectModelCmdlet.resources.dll 30 4.2.1235.0
bin\2070\pt-PT\ObjectModelCmdlet.resources.dll 33 4.2.1235.0
bin\3076\zh-HK\ObjectModelCmdlet.resources.dll 30 4.2.1235.0
bin\3082\es-ES\ObjectModelCmdlet.resources.dll 34 4.2.1235.0
bin\DataProtectionManager.psd1 20  
bin\DataProtectionManager.psm1 25  
bin\1028\zh-TW\Utils.resources.dll 566 4.2.1235.0
bin\1029\cs-CZ\Utils.resources.dll 663 4.2.1235.0
bin\1031\de-DE\Utils.resources.dll 714 4.2.1235.0
bin\1036\fr-FR\Utils.resources.dll 707 4.2.1235.0
bin\1038\hu-HU\Utils.resources.dll 674 4.2.1235.0
bin\1040\it-IT\Utils.resources.dll 674 4.2.1235.0
bin\1041\ja-JP\Utils.resources.dll 806 4.2.1235.0
bin\1042\ko-KR\Utils.resources.dll 704 4.2.1235.0
bin\1043\nl-NL\Utils.resources.dll 642 4.2.1235.0
bin\1045\pl-PL\Utils.resources.dll 702 4.2.1235.0
bin\1046\pt-BR\Utils.resources.dll 665 4.2.1235.0
bin\1049\ru-RU\Utils.resources.dll 1,005 4.2.1235.0
bin\1053\sv-SE\Utils.resources.dll 635 4.2.1235.0
bin\1055\tr-TR\Utils.resources.dll 655 4.2.1235.0
bin\2052\zh-CN\Utils.resources.dll 552 4.2.1235.0
bin\2070\pt-PT\Utils.resources.dll 681 4.2.1235.0
bin\3076\zh-HK\Utils.resources.dll 566 4.2.1235.0
bin\3082\es-ES\Utils.resources.dll 697 4.2.1235.0
bin\1028\SetupLaunchScreen.dll 226 4.2.1235.0
bin\1029\SetupLaunchScreen.dll 234 4.2.1235.0
bin\1031\SetupLaunchScreen.dll 234 4.2.1235.0
bin\1033\SetupLaunchScreen.dll 231 4.2.1235.0
bin\1036\SetupLaunchScreen.dll 235 4.2.1235.0
bin\1038\SetupLaunchScreen.dll 233 4.2.1235.0
bin\1040\SetupLaunchScreen.dll 234 4.2.1235.0
bin\1041\SetupLaunchScreen.dll 228 4.2.1235.0
bin\1042\SetupLaunchScreen.dll 227 4.2.1235.0
bin\1043\SetupLaunchScreen.dll 232 4.2.1235.0
bin\1045\SetupLaunchScreen.dll 235 4.2.1235.0
bin\1046\SetupLaunchScreen.dll 233 4.2.1235.0
bin\1049\SetupLaunchScreen.dll 233 4.2.1235.0
bin\1053\SetupLaunchScreen.dll 232 4.2.1235.0
bin\1055\SetupLaunchScreen.dll 232 4.2.1235.0
bin\2052\SetupLaunchScreen.dll 226 4.2.1235.0
bin\2070\SetupLaunchScreen.dll 233 4.2.1235.0
bin\3076\SetupLaunchScreen.dll 226 4.2.1235.0
bin\3082\SetupLaunchScreen.dll 234 4.2.1235.0
bin\1033\Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.HyperVDatasource.dll 50 4.2.1235.0
bin\1033\Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.SharePoint.dll 59 4.2.1235.0
bin\1033\Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.Exchange.dll 51 4.2.1235.0
bin\1033\Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.ClientDatasource.dll 47 4.2.1235.0
bin\1033\Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.SystemProtection.dll 39 4.2.1235.0
bin\1033\FileSystem.dll 70 4.2.1235.0
bin\Interfaces.dll 21 4.2.1235.0
bin\NativeConfigHelper.dll 379 4.2.1235.0
bin\1033\DpmSetup.dll 1,758 4.2.1235.0
bin\SummaryTE.dll 53 4.2.1235.0
bin\1033\AlertHealthProvider.dll 133 4.2.1235.0
bin\INTENTTRANSLATOR.dll 553 4.2.1235.0
bin\WSS4Cmdlets.dll 163 4.2.1235.0
bin\WSSCmdlets.dll 179 4.2.1235.0
bin\1033\DlsUILibrary.dll 160 4.2.1235.0
XSD\Intent\IMCatalog.xsd 37  
xsd\ProtectionRecoveryManager\StatusMessages.xsd 2  
bin\DsResourceLimits.xml 1  

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2963543
Revision : 2
Created on : 5/20/2020
Published on : 5/20/2020
Exists online : False
Views : 468