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 the hotfix rollup package for System Center Data Protection Manager 2010: November 10, 2010


View products that this article applies to.

Introduction

This article describes the issues in Microsoft System Center Data Protection Manager (DPM) 2010 that are fixed in the Data Protection Manager 2010 hotfix rollup package version 3.0.7706.00 that has a publish date of November 10, 2010.

Note To determine the currently installed version, click the Information icon that is located on the upper-right side of the Main menu bar in the DPM 2010 Administrator Console on the DPM Server.

This hotfix rollup resolves the following issues:
  • You cannot protect the Microsoft Exchange Database Availability Group (DAG) on a secondary DPM 2010 server.
  • You are prompted to restart a client computer after you install an agent on the client.
  • DPM services crash, and you receive the error, "Unable to connect to the database because of a fatal database error."
  • MSDPM crashes, and event ID 945 is logged in the event log.
  • When you change a Protection Group, add a very large database, change the disk allocation, and then commit the Protection Group, DPM 2010 does not honor the user intent, and instead, DPM 2010 sets the sizes of replica and shadow copy volumes to the default sizes.
  • The Management tab does not link to information about the latest Microsoft Knowledge Base article for DPM 2010.
  • You receive the message, "Computers not synchronized," when you try to replicate DPM 2010 databases to a System Center Operations Manager. 

↑ Back to the top


More Information

Hotfix rollup information

Download information

To get the stand-alone package for this update, go to the Microsoft Update Catalog website.

Note This hotfix rollup package applies to all supported language versions of System Center Data Protection Manager 2010.

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites

This hotfix does not replace a previously released hotfix.

↑ Back to the top


Installation instructions

This Data Protection Manager 2010 rollup package consists of three separate updates. To install each update, follow these steps:  
  1. Install the rollup package on the server that is running Data Protection Manager 2010. To do this, run the DataProtectionManager2010-KB2250444.exe file on the server. 

    Note You must restart the Data Protection Manager server after you install this rollup package.
  2. Update the remote Microsoft SQL Server installation that is hosting the DPMDB database. To do this, run the SqlPrep-KB2250444.msp file on the computer that is running SQL Server. 

    Note This step is not required if you are running a SQL Server DPMDB instance on the Data Protection Manager 2010 server.
  3. In the DPM Administrator Console, update the protection agents. To do this, use one of the following methods.

    Method 1: Update the protection agents from the DPM Administrator Console
    1. Open the DPM 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.
    5. In the Enter Credentials and Reboot option dialog box that is displayed, enter your credentials, select the Manually restart the selected servers later option, and then click OK.

      Note You do not have to restart the computer to update the agent. This is why the Manually restart the selected servers later option was selected.
    Method 2: Update the protection agents on the protected computers
    1. Obtain the update protection agent package from the "Data Protection Manager installation location\DPM\Agents\RA\3.0.7706.00" directory on the Data Protection Manager 2010 server.
      • For x86-based updates: i386\1033\DPMAgentInstaller_KB2250444.exe
      • For x64-based updates: amd64\1033\DPMAgentInstaller_KB2250444_AMD64.exe
      Note The DPMAgentInstaller.exe package applies to all languages.
    2. Run the appropriate DPMAgentInstaller.exe package on each protected computer.
    3. Open the DPM Administrator Console on the Data Protection Manager 2010 server. 
    4. Click the Management tab, and then click the Agents tab.
    5. Select the protected computers, and then verify that the agent version is listed as 3.0.7706.00.
  4. Run the DPMManagementShell2007-KB2250444.msp file.

    Note This step is not required if you are running the Data Protection Manager Management Shell on the Data Protection Manager 2010 server.

Restart information

If the DPM Management Shell is open when you install the hotfix rollup package, you must restart the computer. Otherwise, a restart is not required.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2250444
Revision : 4
Created on : 4/20/2020
Published on : 4/20/2020
Exists online : False
Views : 124