Description of hotfix rollup package 6 for System Center Data Protection Manager 2010
This article describes the issues in Microsoft System Center Data Protection Manager (DPM) 2010 that are fixed in hotfix rollup package 6 for System Center DPM 2010.
This hotfix rollup resolves the following issues:
- DPM backup fails for a Microsoft SharePoint farm together with a mirrored content database if the mirrored server name starts with the same name as the principal server name. For example, this issue occurs if the principal server name is "MachineName," the mirrored server name is "MachineName1," and the content database is on a nondefault instance of Microsoft SQL Server.
Additionally, you receive the following error message:Prepare for backup operation for SQL Server database CONTENT_DB_NAME (mirrored between – SQL PRINCIPAL and SQL MIRROR ) on SQL-PRINCIPAL.FQDN has been stopped because this operation depended on another backup operation which failed or was cancelled. (ID 30200)
- Expiry dates for valid datasets that are already written to tape are changed when the retention range is changed during a protection group modification.
A protection group is configured for long-term tape recovery points together with custom long-term recovery goals. Recovery Goal 1 has a smaller retention range than the other recovery goals. In this configuration, if the protection group is changed to remove Recovery Goal 1 and to keep other recovery goals, datasets that were created by Recovery Goal 1 have their retention range changed to the retention range of the other recovery goals.
To avoid this problem, create the IsDatasetExpiryDateChangeInModifyPgAllowed DWORD value under the following registry key, and then set its value data to 0:HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration\MediaManager
- Tapes are not reusable until the day after the day of expiry. This is true because DPM waits until midnight to run the reclamation job that marks tapes as reusable. If a user wants a tape to be reusable on the same day on which it expires, the user should follow these steps:
- Create the following registry key: HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration\MediaManager
- Create the ExpireDatasetOnDayStart 32-bit DWORD value, and then set its value data to 1.
- Create the following registry key:
- DPM does not enable browsing of protected folders on a protected server that has an invalid created date and time.
- A tape backup of millions of files fails, and you receive the following error message: ID 998 Details: The parameter is incorrect (0x80070057).
- Tape colocation that has a high expiry tolerance mixes retention ranges. This causes tapes to expire earlier than expected.
Hotfix rollup information
Download informationThe following file is available for download from the Microsoft Download Center:
Download the Rollup Package 6 for System Center Data Protection Manager 2010
Note This hotfix rollup package applies to all supported language versions of System Center DPM 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 servicesMicrosoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date on which the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
PrerequisitesThe prerequisites for the hotfix rollup package are as follows:
- To install this rollup package on a DPM 2010 server that is running Windows Server 2008 R2, you must have the following hotfix installed:2223201 Event ID 82 may be logged in the System log after you extend the protected dynamic volume on a Windows 7-based or Windows Server 2008 R2-based computer
- To install this rollup package on a DPM 2010 server that is running Windows Server 2008 or Windows Server 2008 Service Pack 2, you must have the following hotfix installed:2279787 Event ID 82 may be recorded in the System log after you extend the protected dynamic volume on a computer that is running Windows Vista or Windows Server 2008
Installation instructionsThis rollup package consists of three separate updates. To install each update, follow these steps:
- Before you install any update, make a backup of the DPM database.
- Install the rollup package on the server that is running DPM 2010. To do this, run the DataProtectionManager2010-KB2718797.exe file on the server.
Note You may have to restart the DPM server after you install this rollup package.
- 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
- Open the DPM Administrator Console.
- Click the Management tab, and then click the Agents tab.
- In the Protected Computer list, select a computer, and then click Update on the Action pane.
- Click Yes, and then click Update Agents.
Note A restart might be required for agent upgrades.
Method 2: Update the protection agents on the protected computers
- Obtain the update protection agent package from the "Data Protection Manager installation location\DPM\Agents\RA\3.0.7707.00" directory on the DPM 2010 server.
- For x86-based updates: i386\1033\DPMAgentInstaller_KB2718797.exe
- For x64-based updates: amd64\1033\DPMAgentInstaller_KB2718797_AMD64.exe
- Run the appropriate DPMAgentInstaller.exe package on each protected computer.
- Open the DPM Administrator Console on the DPM 2010 server.
- Click the Management tab, and then click the Agents tab.
- Select the protected computers, and then verify that the agent version is listed as "3.0.8193.00."
Article ID: 2718797 - Last Review: 07/26/2012 07:35:00 - Revision: 2.0
Microsoft System Center Data Protection Manager 2010
- kbqfe kbfix kbexpertiseinter atdownload kbsurveynew KB2718797