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 version 2.0.8864.0 that has a publish date of March 31, 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 2007 Administrator Console on the DPM Server.
This hotfix rollup resolves the following issues:
- You may experience a crash in the Data Protection Manager engine when you run a tape job from a protected server.
- When you use the Data Protection Manager Management Console to browse Microsoft SharePoint Server recovery points or when you back up a SharePoint point to tape from disk, you receive the following error message:
- A SharePoint recovery point in a secondary Data Protection Manager has a different set of datasets than the corresponding recovery point in the primary Data Protection Manager.
- Alerts for standby continuous replication (SCR) servers are not displayed in Microsoft Operations Manager.
- Default disk allocations may grow unexpectedly for system state protection.
- When you restore a SharePoint site that contains a WEB host header to an alternate location, the site is restored to the default site.
- Shared Services Provider (SSP) database protection is blocked when one or more SSP names begin with the same SSP name.
- The server is slow, and time-out errors may occur, when you run a backup-to-tape job.
- Data Protection Manager-owned tapes are marked as unrecognized.
- Data Protection Manager cannot retrieve SharePoint catalog information. Therefore, item-level recovery is not possible for some content databases. Additionally, you may receive the following error code:
- You receive the following protection agent error code when bulk tape jobs cannot be completed successfully:
- You may experience a Data Protection Manager engine crash during backup to tape.
- The Data Protection Manager Management Console does not display recovery points before the year 2010 in some scenarios.
This hotfix rollup also includes all previously released hotfix 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
A hotfix rollup package is available for System Center Data Protection Manager 2007: October 23, 2009
Hotfix rollup information
The following file is available for download from the Microsoft Download Center:
System Center Data Protection Manager 2007 hotfix package (32-bit x86-based and 64-bit x64-based versions)Download the System Center Data Protection Manager 2007 hotfix package now.Note
This hotfix rollup package applies to all supported language versions of System Center Data Protection Manager 2007.
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.
After you install this hotfix rollup, backups may not be completed successfully. Additionally, you may receive the following error message:
DPM has detected that some other application has created recovery points on the recovery point volume for datasource_name for server server_name. Future backups will fail until these recovery points are deleted.
Recommended Action: Open the DPM Management Shell and run .\Delete-Shadowcopy.ps1 "volume name" to delete the externally created recovery points on the recovery point volume.
This error message indicates that a shadow copy association is corrupted on the DPM server and could lead to loss of data. This hotfix rollup makes sure that the backup succeeds only when the association is correct. When the shadow copy association is correct, this condition does not occur for future backups.
To correct the shadow copy association, use one of the following methods.Method 1
Migrate the data to different volumes by using the MigrateDatasourceDataFromDPM command-line script. For more information, visit the following Microsoft TechNet Web site:Method 2
Redo the initial replica on a different DPM server to re-protect the protected server.Method 3
Enable the AllowBackupOnSCRemap subkey in the registry. This method enables backups to continue even if the shadow copy association is incorrect. We do not recommend that you enable this registry subkey. However, if you must have backups to run, you can do this as a temporary measure.Important
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
How to back up and restore the registry in Windows
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click to select the following registry subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Data Protection Manager\Configuration\TaskExecutionOptions
- Right-click AllowBackupOnSCRemap, and then click Modify.
- In the Value data box, type 1, and then click OK.
- On the File menu, click Exit to exit Registry Editor.
The following list contains prerequisites for the hotfix rollup:
- You must have System Center Data Protection Manager 2007 Service Pack 1 installed.
- You must have critical update KB962975 installed.
For more information about System Center Data Protection Manager 2007 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
Description of System Center Data Protection Manager 2007 Service Pack 1
For more information about critical update KB962975, click the following article number to view the article in the Microsoft Knowledge Base:
Dynamic disks are marked as "Invalid" on a computer that is running Windows Server 2008 or Windows Vista when you bring the disks online, take the disks offline, or restart the computer if Data Protection Manager is installed