The hotfix that is described here is included in the update that is described in the following Microsoft Knowledge Base article:
Description of the latest hotfix rollup package for System Center Data Protection Manager 2007: March 29, 2010
We highly recommend that you install this update to resolve the problem described in this article and other DPM-related issues.
This article describes the issues in Microsoft System Center Data Protection Manager (DPM) 2007 that are fixed in the Data Protection Manager 2007 hotfix rollup package that is dated October 23, 2009.
This rollup resolves the following issues.
The DPM 2007 error logs are flushed only when the DPM service starts or stops. If the DPM service crashes, the DPM error logs are not flushed. This behavior causes some errors to be missing from the error logs.Note
After you apply this hotfix rollup, the DPM error logs are flushed every five minutes. The error logs are also flushed when the DPM service stops or crashes.
The DPM SQL Server database causes Microsoft SQL Server exceptions that are not captured in DPM traces.
Express full backup may take several hours to run if the DPM server is configured to protect more than 100 SQL Server databases.
The DPM administrator console does not open when multiple backup jobs concurrently access a tape library.
When library sharing is enabled, the GlobalDbConnectionString registry value may point to the local computer and not to the global SQL Server installation after a post-DPM 2007 Service Pack 1 rollup is installed.
A job may freeze before it transfers data if the DsRoleGetPrimaryDomainInformation
The DPM administrator console may not open if the Disconnect-DPMServer PowerShell cmdlet runs during a new tape backup job.
When DPM protects mirrored SQL Server databases that are clustered, the old volume bitmaps are not deleted. Therefore, the 128-volume bitmap limit may be exceeded.
This hotfix also includes all previously released rollups for Data Protection Manager 2007 Service Pack 1 (SP1):
A replica may be listed as inconsistent after you install System Center Data Protection Manager 2007 Service Pack 1 on a computer that is running an x64-based version of Windows Server 2003
Description of the hotfix rollup package for System Center Data Protection Manager 2007: February 16, 2009
Description of the hotfix rollup package for System Center Data Protection Manager 2007: April 14, 2009
Description of the hotfix rollup package for System Center Data Protection Manager 2007: June 4, 2009
A hotfix rollup package is available for System Center Data Protection Manager 2007: August 28, 2009
The following file is available for download from the Microsoft Download Center:Download the System Center Data Protection Manager 2007 hotfix package now.
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
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.Note
This hotfix package applies to all DPM 2007 languages.
To install this rollup package, you must have DPM 2007 Service Pack 1 installed.
This DPM 2007 rollup package contains three separate updates. To install each update, follow these steps:
- Install the rollup package on the server that is running DPM 2007 Service Pack 1. To do this, run the DataProtectionManager2007-KB976542.exe file on the server.
Notes You may have to restart the DPM server if the DPM administrator console or DPM Management Shell is open when you install the rollup.
You cannot install the rollup package if there is insufficient disk space to back up the DPM SQL Server database. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Error message when you try to install a System Center Data Protection Manager 2007 update: "DPM installation has failed"
- Update the remote SQL Server installation that hosts the DPMDB database. To do this, run the SqlPrep-KB976542.msp file on the computer that is running SQL Server.
Note This step is not required if you are running an instance of the SQL Server DPMDB database on the DPM 2007 server.
- Update the protection agents that are in the DPM administrator console. To do this, use one of the following methods:
Method 1: Update the protection agents from the DPM administrator console
Method 2: Update the protection agents on the protected computers
- Open the DPM administrator console.
- Click the Management tab, and then click the Agents tab.
- Select a computer from the Protected Computer list, and then click Update on the Action pane.
- Click Yes, and then click Update Agents.
- In the Enter Credentials and Reboot option dialog box, enter your credentials, select Manually restart the selected servers later, and then click OK.
Note You do not have to restart the computer to update the protection agents.
- Obtain one of the follwoing Update Protection Agent packages from the DPM installation location in the DPM\Agents\RA\2.0.8861.0 folder on the DPM 2007 server:
x86 update: i386\1033\DPMAgentInstaller_KB976542.exe
x64 update: amd64\1033\DPMAgentInstaller_KB976542_AMD64.exe
Note The DPMAgentInstaller.exe package applies to all languages.
- Run the appropriate DPMAgentInstaller.exe package on each computer that is protected.
- Open the DPM administrator console that is located on the DPM 2007 server.
- Click the Management tab, and then click the Agents tab.
- Select the computers that are protected, and then verify that the agent version is listed as 2.0.8861.0.
- Run the DPMManagementShell2007-KB976542.msp file.
Note This step is not required if you are running DPM Management Shell on the DPM 2007 server.