You are currently offline, waiting for your internet to reconnect

Update Rollup 4 for System Center 2012 R2 Data Protection Manager

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

Issues that are fixed in this update rollup

Data Protection Manager

The following issues are fixed in this update:
  • Item level recovery does not restore custom permissions when Microsoft SharePoint is running localized language packs.

    Scenario
    You try to back up SharePoint when SharePoint has various files that have custom access permission settings and is using a non-English locale for SharePoint sites. When you try to recover the files, data is recovered successfully. However, the custom permissions may be lost. This causes some users to no longer have access to the file until permissions are restored by the SharePoint administrator.
  • The DPM user interface crashes, and you receive the following error message:
    Connection to the DPM service has been lost.

    This issue occurs when you change some protection groups after you upgrade to DPM 2012 R2 Update Rollup 2 or a later version.
  • You experience issues when you try to restore a SQL Server database that has error 0x800423f4.

    Scenario
    You have a SQL Server database that uses multiple mount points that point to the same volume and that protect it by using DPM. When you try to recover from an existing recovery point, you receive an error message 0x800423f4.
  • An instance of SQL Server is missing when you try to create a protection group (PG).

    Scenario 
    You have two or more instances of SQL Server on same server so that one of the database names in one instance is a substring of another name of an instance of SQL Server. For example, you have a default instance of SQL Server and another instance that is named "contosoinstance." Then, you create a database that is named "contosoins" in the default instance of SQL Server.

    In this case, when you try to create or change a protection group, the “contosoinstance” SQL instance and its database do not appear in the Create Protection Group Wizard.
  • The DPM console or service crash after VMs are removed from the Hyper-V host.

    Scenario
    Several virtual machines on the Hyper-V host are physically removed. Then, the DPM UI crashes when you try to stop protection for these virtual machines.
  • DPM crashes with NullReferenceException.

    Scenario
    When you protect a SQL database by using long-term protection on tape, the SQL logs are moved to a different disk volume. When you try to make a backup for the first time after you move the logs, the DPM UI crashes. However after you restart the UI, everything works correctly.
  • Scheduled backup to tape runs on an incorrect date for quarterly, semi-annually, and yearly backups. In some cases, you see that the backup runs before the specific date.
  • The DPM UI sometimes crashes when you change a protection group that has the following error:
    Connection to the DPM service has been lost. (ID: 917)

Features that are implemented in this update rollup

  • Added support for protecting SQL Server 2014

    This update let you protect SQL Server 2014 as a workload. There is no change in the user experience or in scenarios that are supported. Therefore, you can continue to back up SQL Server 2014 by using DPM in the same way that you protected older versions of SQL Server.

  • Unsupported scenarios in SQL Server 2014
    • You cannot use SQL Server 2014 as the DPM configuration database.
    • You cannot back up the data that is stored as Windows Azure blobs from SQL Server 2014.
    • The "Prefer secondary backup" preference for the SQL Always On option is not supported completely. DPM always takes a backup from the secondary. If no secondary can be found, the backup fails.
  • Added support for SQL Server 2012 Service Pack 2 (SP2)

    This update lets you protect the latest SQL Server 2012 SP2 as a workload and also use it as a DPM configuration database. There is no change in the user experience or scenarios that are supported. Therefore, you can continue to back up SQL Server 2012 SP2 by using DPM in the same way that you protected older SQL Server versions.

  • Simplified steps for Online backup registration

    Note Existing DPM to Azure customers should upgrade to the latest agent (version 2.0.8689.0 or a later version available here). In case this is not installed, online backups fail, and no DPM to Azure operations will work.

    By adopting the latest new features and improvements in this update, DPM customers can register for Azure protection in several clicks. These new features and improvements remove the dependency of creating a certificate by using makecert and uploading it to the Azure portal. Instead, you can download vault credentials from the vault page on the Azure portal and use those credentials for registration.

    To register the DPM server to the Azure backup vault, follow these steps.

    Prerequisites
    You must have a subscription on the Azure portal, and a backup vault must be created on the portal.

    If you already use DPM-A
    1. From the backup vault page on the portal, download the agent for SC Data Protection Manager.
    2. Run the installer on the server. To do this, follow these steps:
      1. Select the folder to install the server.
      2. Enter the correct proxy settings.
      3. Opt in for Microsoft updates, if you are not already opted in. Critical updates are usually propagated through Microsoft updates.
      4. The installer verifies the prerequisite software and installs them. 

    Please be aware that you do not have to register the server again if the server is already registered and backups are in progress. In this case, you have only to upgrade the agent.

    Getting started with DPM-A
    1. From the backup vault page on the portal, follow these steps:
      1. Download vault credentials.
      2. Download the agent for System Center Data Protection Manager. 
    2. Run the installer on the server. To do this, follow these steps:
      1. Select the folder where you want to install the agent.
      2. Enter the correct proxy settings.
      3. Opt in for Microsoft updates, if you have not already opted in. Critical updates are usually propagated through Microsoft updates.
      4. The installer will verify the prerequisite software and installs them.
    3. Register the DPM server. To do this. follow these steps:
      1. In Data Protection Manager, click Online, and then click Register Server.
      2. In the Registration window, select the vault credential file that is downloaded from the portal. In the case of a remote scenario, only the network share path is enabled.
      3. Follow the rest of the steps, and complete the registration. 

How to obtain and install Update Rollup 4 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 the 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

The following file is available for manual download from the Microsoft Download Center:


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.

    Note Before you install this update through Microsoft Update, the Data Protection Manager Administrator Console should be closed. You may have to restart the Data Protection Manager server after you install this update rollup package.
  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 4 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.1273.0

      The installation packages are as follows:
      • For x86-based updates: i386\1033\DPMProtectionAgent_KB3009516.msp
      • For x64-based updates: amd64\1033\DPMProtectionAgent_KB3009516 _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.1273.0.

    Method 3: Update the protection agents on Windows Server 2003 servers

    Install the Windows Server 2003 agent to protect Windows Server 2003 servers by using Update Rollup 4 for Data Protection Manager 2012 R2. To do this, follow these steps:
    1. Install the Microsoft Visual C++ 2008 redistributable on Windows Server 2003 servers, if it is not already installed.

      Note If the C++ redistributable is not installed, you receive the following error message :
      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.1273.0\amd64\1033\DPMAgentInstaller_Win2K3_AMD64.exe
      • 32-bit:DPM_Installation_Location\DPM\agents\RA\4.2.1273.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 to the DPM server:

      Attach-ProductionServer.ps1 DPMServerNameProductionServerNameUserNamePasswordDomain
    5. On the DPM server, click Refresh two times on the agent that is connected to the management UI. Then, validate that the Health Service state is initialized.

Important information
  1. We recommend that you restart the protected computer after you apply the Update Rollup 4 agent update.
  2. If protected computers are not restarted after you apply Update Rollup 4, the following things can occur:
    • On Hyper-V/Windows Server 2012 R2 infrastructure, restart the computer (Protected_Computer) or other cluster nodes if VM backup jobs fail and generate either of the following error messages:
      Protected_Computer needs to be restarted. This may be because the computer has not been restarted since the protection agent was installed. (ID 48 Details: The parameter is incorrect (0x80070057))

      DPM failed to communicate with Protected_Computer because of a communication error with the protection agent. (ID 53 Details: Not implemented (0x80000001))
    • When you select a data source from the Protected Computer that was added after you apply Update Rollup 4, the Create Protection Group action may fail and generate an error message that resembles any of the following.

      Note To avoid this problem, restart the computer (Protected_Computer).
      • FileSystem or Hyper Datasource

        FileSystem or Hyper Datasource

      • SQL Datasource

        SQL Datasource

      • SharePoint Datasource

        SharePoint Datasource

      • Exchange Datasource

        Exchange Datasource


Files that are updated

File nameFile sizeFile version
Utils.dll1204 KB4.2.1273.0
Utils.dll1204 KB4.2.1273.0
Microsoft.EnterpriseStorage.Dls.Prm.dll2448 KB4.2.1273.0
CPWrapper.dll1078 KB4.2.1273.0
RecoveryPage.dll1766 KB4.2.1273.0
DPMRA.exe5531 KB4.2.1273.0
dpmac.exe1823 KB4.2.1273.0
Inspect.dll161 KB4.2.1273.0
DsmFs.dll943 KB4.2.1273.0
ObjectModel.dll1211 KB4.2.1273.0
cs-CZ\ObjectModel.resources.dll30 KB4.2.1273.0
de-DE\ObjectModel.resources.dll30 KB4.2.1273.0
es-ES\ObjectModel.resources.dll30 KB4.2.1273.0
fr-FR\ObjectModel.resources.dll30 KB4.2.1273.0
hu-HU\ObjectModel.resources.dll30 KB4.2.1273.0
it-IT\ObjectModel.resources.dll30 KB4.2.1273.0
ja-JP\ObjectModel.resources.dll31 KB4.2.1273.0
ko-KR\ObjectModel.resources.dll30 KB4.2.1273.0
nl-NL\ObjectModel.resources.dll29 KB4.2.1273.0
pl-PL\ObjectModel.resources.dll30 KB4.2.1273.0
pt-BR\ObjectModel.resources.dll30 KB4.2.1273.0
pt-PT\ObjectModel.resources.dll30 KB4.2.1273.0
ru-RU\ObjectModel.resources.dll34 KB4.2.1273.0
sv-SE\ObjectModel.resources.dll29 KB4.2.1273.0
tr-TR\ObjectModel.resources.dll30 KB4.2.1273.0
zh-CN\ObjectModel.resources.dll29 KB4.2.1273.0
zh-HK\ObjectModel.resources.dll29 KB4.2.1273.0
zh-TW\ObjectModel.resources.dll29 KB4.2.1273.0
Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.SQL.dll50 KB4.2.1273.0
vssnullprovider.dll72 KB4.2.1273.0
null_ps.dll18 KB4.2.1273.0
SetupUtilv2.dll604 KB4.2.1273.0
ClusterInquiry.dll197 KB4.2.1273.0
VssRequestor.dll346 KB4.2.1273.0
DpmWriterHelperPlugin.dll514 KB4.2.1273.0
ExchangeWriterHelperPlugin.dll802 KB4.2.1273.0
FileWriterHelperPlugin.dll583 KB4.2.1273.0
GenericDatasourceWriterHelperPlugin.dll779 KB4.2.1273.0
GenericNonVssDatasourceHelperPlugin.dll700 KB4.2.1273.0
SpSearchWriterHelperPlugin.dll602 KB4.2.1273.0
SQLWriterHelperPlugin.dll959 KB4.2.1273.0
WSSWriterHelperPlugin.dll768 KB4.2.1273.0
HypervVhdHelper.dll81 KB4.2.1273.0
DpmoVhdManager.dll93 KB4.2.1273.0
HypervVhdManager.dll132 KB4.2.1273.0
WSSCmdletsWrapper.exe198 KB4.2.1273.0
DPMLA.exe2481 KB4.2.1273.0
Microsoft.EnterpriseStorage.Dls.Prm.MbcParser.dll447 KB4.2.1273.0
DpmBackup.exe360 KB4.2.1273.0
DpmWriter.exe611 KB4.2.1273.0
FSPathMerge.exe301 KB4.2.1273.0
AgentProxy.dll232 KB4.2.1273.0
DPMFSFilterWrapperDLL.dll153 KB4.2.1273.0
SetAgentCfg.exe143 KB4.2.1273.0
SetupDpmfltr.dll111 KB4.2.1273.0
TERuntime.dll108 KB4.2.1273.0
EngineUICommon.dll505 KB4.2.1273.0
EngineUICommon.dll505 KB4.2.1273.0
AutoHeal.dll61 KB4.2.1273.0
ObjectModelCmdlet.dll386 KB4.2.1273.0
cs-CZ\ObjectModelCmdlet.resources.dll31 KB4.2.1273.0
de-DE\ObjectModelCmdlet.resources.dll33 KB4.2.1273.0
es-ES\ObjectModelCmdlet.resources.dll33 KB4.2.1273.0
fr-FR\ObjectModelCmdlet.resources.dll33 KB4.2.1273.0
hu-HU\ObjectModelCmdlet.resources.dll33 KB4.2.1273.0
it-IT\ObjectModelCmdlet.resources.dll32 KB4.2.1273.0
ja-JP\ObjectModelCmdlet.resources.dll34 KB4.2.1273.0
ko-KR\ObjectModelCmdlet.resources.dll33 KB4.2.1273.0
nl-NL\ObjectModelCmdlet.resources.dll31 KB4.2.1273.0
pl-PL\ObjectModelCmdlet.resources.dll32 KB4.2.1273.0
pt-BR\ObjectModelCmdlet.resources.dll32 KB4.2.1273.0
pt-PT\ObjectModelCmdlet.resources.dll32 KB4.2.1273.0
ru-RU\ObjectModelCmdlet.resources.dll39 KB4.2.1273.0
sv-SE\ObjectModelCmdlet.resources.dll31 KB4.2.1273.0
tr-TR\ObjectModelCmdlet.resources.dll31 KB4.2.1273.0
zh-CN\ObjectModelCmdlet.resources.dll29 KB4.2.1273.0
zh-HK\ObjectModelCmdlet.resources.dll29 KB4.2.1273.0
zh-TW\ObjectModelCmdlet.resources.dll29 KB4.2.1273.0
DataProtectionManager.psd119 KB
DataProtectionManager.psm124 KB
cs-CZ\Utils.resources.dll665 KB4.2.1273.0
de-DE\Utils.resources.dll716 KB4.2.1273.0
es-ES\Utils.resources.dll699 KB4.2.1273.0
fr-FR\Utils.resources.dll709 KB4.2.1273.0
hu-HU\Utils.resources.dll730 KB4.2.1273.0
it-IT\Utils.resources.dll676 KB4.2.1273.0
ja-JP\Utils.resources.dll808 KB4.2.1273.0
ko-KR\Utils.resources.dll706 KB4.2.1273.0
nl-NL\Utils.resources.dll644 KB4.2.1273.0
pl-PL\Utils.resources.dll703 KB4.2.1273.0
pt-BR\Utils.resources.dll667 KB4.2.1273.0
pt-PT\Utils.resources.dll683 KB4.2.1273.0
ru-RU\Utils.resources.dll1007 KB4.2.1273.0
sv-SE\Utils.resources.dll637 KB4.2.1273.0
tr-TR\Utils.resources.dll657 KB4.2.1273.0
zh-CN\Utils.resources.dll555 KB4.2.1273.0
zh-HK\Utils.resources.dll568 KB4.2.1273.0
zh-TW\Utils.resources.dll568 KB4.2.1273.0
Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.HyperVDatasource.dll49 KB4.2.1273.0
Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.SharePoint.dll58 KB4.2.1273.0
Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.Exchange.dll50 KB4.2.1273.0
Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.ClientDatasource.dll46 KB4.2.1273.0
Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.SystemProtection.dll38 KB4.2.1273.0
FileSystem.dll69 KB4.2.1273.0
Interfaces.dll20 KB4.2.1273.0
Interfaces.dll20 KB4.2.1273.0
NativeConfigHelper.dll378 KB4.2.1273.0
NativeConfigHelper.dll378 KB4.2.1273.0
DpmSetup.dll1757 KB4.2.1273.0
SummaryTE.dll55 KB4.2.1273.0
AlertHealthProvider.dll132 KB4.2.1273.0
AlertHealthProvider.dll132 KB4.2.1273.0
IntentTranslator.dll557 KB4.2.1273.0
IntentTE.dll15 KB4.2.1273.0
WSS4Cmdlets.dll162 KB4.2.1273.0
WSSCmdlets.dll178 KB4.2.1273.0
DLSUILibrary.dll159 KB4.2.1273.0
CMTE.dll180 KB4.2.1273.0
WizardUI.dll3183 KB4.2.1273.0
MsdpmDll.dll572 KB4.2.1273.0
AMEngineService.dll92 KB4.2.1273.0
ServiceProxy.dll361 KB4.2.1273.0
EngineServiceProxyWrapper.dll162 KB4.2.1273.0
EngineServiceProxyWrapper.dll162 KB4.2.1273.0
ProtectionView.dll871 KB4.2.1273.0
DiskAllocationControl.dll125 KB4.2.1273.0
CloudEngineProxyWrapper.dll39 KB4.2.1273.0
CBEngineServiceProxy.dll103 KB4.2.1273.0
msdpmPS.dll74 KB4.2.1273.0
UICommon.dll95 KB4.2.1273.0
cs-CZ\WizardUI.resources.dll1785 KB4.2.1273.0
de-DE\WizardUI.resources.dll1791 KB4.2.1273.0
es-ES\WizardUI.resources.dll1790 KB4.2.1273.0
fr-FR\WizardUI.resources.dll1793 KB4.2.1273.0
hu-HU\WizardUI.resources.dll1795 KB4.2.1273.0
it-IT\WizardUI.resources.dll1788 KB4.2.1273.0
ja-JP\WizardUI.resources.dll1804 KB4.2.1273.0
ko-KR\WizardUI.resources.dll1788 KB4.2.1273.0
nl-NL\WizardUI.resources.dll1787 KB4.2.1273.0
pl-PL\WizardUI.resources.dll1787 KB4.2.1273.0
pt-BR\WizardUI.resources.dll1787 KB4.2.1273.0
pt-PT\WizardUI.resources.dll1790 KB4.2.1273.0
ru-RU\WizardUI.resources.dll1833 KB4.2.1273.0
sv-SE\WizardUI.resources.dll1781 KB4.2.1273.0
tr-TR\WizardUI.resources.dll1785 KB4.2.1273.0
zh-CN\WizardUI.resources.dll1772 KB4.2.1273.0
zh-HK\WizardUI.resources.dll1774 KB4.2.1273.0
zh-TW\WizardUI.resources.dll1774 KB4.2.1273.0
cs-CZ\WizardUI.resources.dll1785 KB4.2.1273.0
de-DE\WizardUI.resources.dll1791 KB4.2.1273.0
es-ES\WizardUI.resources.dll1790 KB4.2.1273.0
fr-FR\WizardUI.resources.dll1793 KB4.2.1273.0
hu-HU\WizardUI.resources.dll1795 KB4.2.1273.0
it-IT\WizardUI.resources.dll1788 KB4.2.1273.0
ja-JP\WizardUI.resources.dll1804 KB4.2.1273.0
ko-KR\WizardUI.resources.dll1788 KB4.2.1273.0
nl-NL\WizardUI.resources.dll1787 KB4.2.1273.0
pl-PL\WizardUI.resources.dll1787 KB4.2.1273.0
pt-BR\WizardUI.resources.dll1787 KB4.2.1273.0
pt-PT\WizardUI.resources.dll1790 KB4.2.1273.0
ru-RU\WizardUI.resources.dll1833 KB4.2.1273.0
sv-SE\WizardUI.resources.dll1781 KB4.2.1273.0
tr-TR\WizardUI.resources.dll1785 KB4.2.1273.0
zh-CN\WizardUI.resources.dll1772 KB4.2.1273.0
zh-HK\WizardUI.resources.dll1774 KB4.2.1273.0
zh-TW\WizardUI.resources.dll1774 KB4.2.1273.0
dpmfilter.inf2 KB
DpmFilter.cat8 KB
DsResourceLimits.xml0 KB

Properties

Article ID: 3009516 - Last Review: 10/29/2014 19:56:00 - Revision: 3.0

Microsoft System Center 2012 R2 Data Protection Manager

  • kbfix kbqfe kbexpertiseinter kbsurveynew atdownload KB3009516
Feedback
t=">tml>mp;did=1&t=">