Article ID: 968579 - View products that this article applies to.
This article describes the Microsoft System Center Data Protection Manager (DPM) 2007 issues that are fixed in the Data Protection Manager 2007 hotfix rollup package that is dated April 14, 2009.
Important The hotfix that is described here is included in the update that is described in the following Microsoft Knowledge Base article:
979970We highly recommend that you install this update to resolve the problem described in this article and other DPM-related issues.
(http://support.microsoft.com/kb/979970/ )Description of the latest hotfix rollup package for System Center Data Protection Manager 2007: March 29, 2010
This rollup addresses the following issues:
If you are protecting Hyper-V servers by using both primary and secondary protection, the DPM Administrator console may crash if you try to protect additional data sources.
DPM fails to enumerate mailboxes when the Exchange users and the Exchange Servers are in different domains.
Creating or changing the disk allocation for a data source in a Protection Group may fail on a Data Protection Manager server that is running an x64-based version of Windows Server 2008. In this case, you receive the following error message:
Error 360: The operation failed due to a virtual disk service error
Error details: Unknown error (0x80042515)
If you select the "Recover to the original location" and "Apply security" settings of the recovery point version options when you restore a directory from backup, the NTFS file system permissions on the directory are not restored correctly.
When you try to protect data sources on a Windows Server 2003-based or Windows Server 2008-based cluster, the shared volumes on the cluster may be listed under the wrong resource groups.
FilesNotToBackupregistry key on a protected server contains values that are longer than 260 characters or data that is longer than 8K, you receive the following error:
The replica of Volume G:\ on <server name> is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent (ID 3106) An unexpected error occurred during job execution. (ID 104 Details: More data is available (0x800700EA))
Restoring a Windows SharePoint Services-related content database that is detached from the server farm fails with a 0x80070003 error.
If Windows SharePoint Services 3.0 is configured to connect to the content database by using a Microsoft SQL Server alias and if SharePoint rollup package 957691 is installed on the SharePoint server, Data Protection Manager cannot protect the content databases. In this scenario, you receive the following error message:
This Windows SharePoint Services farm cannot be protected because DPM did not find any dependent databases and search indices to be protected. (ID: 32008)
SharePoint catalog generation fails with a "The number of WaitHandles must be less than or equal to 64" message.
The DpmDriveMappingTool.exe command-line tool cannot run in Windows Server 2008 and generates a 0x80070424 error.
If library sharing is enabled and the global database server is down, you cannot point to the local database using the SetSharedDpmDatabase.exe tool.
"Backup to tape failed" alerts disappear if the DPM Administrator console is closed and re-opened.
Secondary protection fails with the following error:
DPM could not start a recovery, consistency check, or initial replica creation job for <data source type> <data source name> on <server name> for following reason: (ID: 3170) The operation failed for <data source type> on <server name> because the data source is not available. (ID: 30169) DPM ID: 3|Unable to configure protection|
Synchronization job fails with "0x80070057" if the protected server has files or directories that are using reserved names.
Update informationThe following files are available for download from the Microsoft Download Center:
System Center Data Protection Manager 2007 hotfix package (32-bit and 64-bit versions)
Download the 968579 package now.
Collapse this imageExpand this image
Note The update package applies to all Data Protection Manager 2007 languages.
PrerequisitesTo apply this update, you must have Data Protection Manager 2007 Service Pack 1 installed on the computer.
Note You must install the rollup package in the following KB article for applying the rollup package of this article:
(http://support.microsoft.com/kb/963102/ )Description of the hotfix rollup package for System Center Data Protection Manager 2007: February 16, 2009
Restart requirementYou must restart the Data Protection Manager server after you install this rollup package.
Update replacement informationThis update does not replace any other updates.
File informationThe English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
For the 32-bit version
Collapse this tableExpand this table
For the 64-bit version
Collapse this tableExpand this table
Installation instructionsThis Data Protection Manager 2007 rollup package consists of three separate updates. To install each update, follow these steps:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates