HOTFIX: Hotfix rollup package 7 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 7 for System Center DPM 2010.
This hotfix rollup resolves the following issues:

• When a Microsoft SharePoint site collection name contains a space, SharePoint item-level recovery fails in System Center Data Protection Manager 2010.
  For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:

  2755678 SharePoint item-level recovery fails when the site collection name contains a space in System Center Data Protection Manager 2010

• After you rename a SharePoint site in System Center Data Protection Manager 2010, you cannot restore the site.
  For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:

  2763004 System Center Data Protection Manager 2010 is unable to restore SharePoint after renaming a site

• In System Center Data Protection Manager 2010, the SharePoint Recovery Point Status report displays incorrect data.
  For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:

  2763010 System Center Data Protection Manager 2010 SharePoint Recovery Point Status Report shows stale data

Source and Download link

EUR not working in combination with DFS

It is not possible for users to restore (their own) files using EUR in situations where DFS (Distributed File System) is in place for the file servers.

Users receive the error message: "There are no previous versions available."

CausePrevious versions of a file or of a folder in a DFS share are not listed if you access the share through a nested DFS link from a computer that is running Windows 7 or Windows Server 2008 R2.

Hotfix
A supported hotfix is available from Microsoft for the following Operating Systems.

• Windows 7
• Windows 7 Service Pack 1 (SP1)
• Windows Server 2008 R2
• Windows Server 2008 R2 Service Pack 1 (SP1)

The hotfix is available using this Support link: http://support.microsoft.com/default.aspx?scid=kb;EN-US;2466048

Our experienceThe support article describes that this issue only occurs when you try to access the share by DFS name. <\\DFS\fileshare> When you access the share by the file server name it should work. <\\fileserver\fileshare>. However we experienced the issue also when accessing the share using the server name. Both issues where solved by the hotfix.

More info about End User Recovery (EUR)

Volsnap Bluescreen on DPM Server

You might run in to the situation that you DPM 2010 server has a BSOD now and then. If this case you should check the stop error that is returned.

Check if the following Stop errors is returned when you create a snapshot of a volume:

STOP: 0x0000007E (parameter1, parameter2, parameter3, parameter4) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Stop 0x00000050 (parameter1 , parameter2 , parameter3 , parameter4 ) PAGE_FAULT_IN_NONPAGED_AREA

You may experience this issue after you enable shadow copy functionality on a volume that is configured with a secondary Data Protection Manager (DPM) server for backup.

Hot Fix available
Microsoft has released a Hotfix for this issue. http://support.microsoft.com/kb/2460912/en-us

This applies to

• Windows Server 2008 R2
• Windows Server 2008 R2 Service Pack 1 (SP1)

DPM agent versions

DPM 2010

DPM 2010 3.0.7696.0 DPM 2010 role-up 1 (KB2250444) 3.0.7706.00 DPM 2010 role-up 2 (KB2465832) 3.0.7707.0

DPM 2007

DPM 2007 SP0 - 2.0.5820.0 DPM 2007 SP1 - 2.0.8793.0 DPM 2007 SP1 (with KB 968579) 2.0.8836.0 DPM 2007 SP1 (with KB970867) 2.0.8840.0 DPM 2007 SP1 (with KB970867 Revision: 1.0) 2.0.8851.0 DPM 2007 SP1 (with KB979970 ) 2.0.8864

System Center Data Protection Manager 2010 QFE Rollup [KB 2250444]

There is a rollup packages for DPM 2010 available.

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.

* A reboot of the DPM server is required.
*The protected servers do not need a reboot.

Agent update failed

After installing the new Hotfix rollup package for DPM 2007 (KB979970) you have to update the agents. In my case this went fine for almost all agents.
Only the agents on the SharePoint servers had a nasty issue.

The (push) upgrade failed with the following error.

Agent Operation failed (ID 370)
The agent operation fauled because an error occurred wile running the installation program on <compter name> (ID 313). Details: The installation source for the product is not available. Verify that the source exits anf that you can access it (ox8007064c)
-----------------
The local agent installation shows a same kind of error:

DPMAgentInstaller failed with errorcode =8007064c, error says: The installation source for this product is not available.  Verify that the source exists and that you can access it.

Check log files in [WINDIR]Temp\MSDPM*.LOG
Press Enter key to close the window
-----------------
For this error messages it is not clear which installation files are missing.

The log MSDPMAgentPatchInstall.LOG (windir\temp) shows in more detail which files are required.
--------------------------
SI (s) (8C:D0) [13:27:58:789]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (8C:D0) [13:27:58:789]: Note: 1: 1706 2: -2147483647 3: dpmra.msi
MSI (s) (8C:D0) [13:27:58:789]: SOURCEMGMT: Processing net source list.
MSI (s) (8C:D0) [13:27:59:810]: SOURCEMGMT: Now checking product {07CCDE6A-1D92-2C9C-D091-9E682643ABCC}
MSI (s) (8C:D0) [13:27:59:810]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (8C:D0) [13:27:59:810]: SOURCEMGMT: Trying source C:\WINDOWS\Microsoft Data Protection Manager\DPM\Agents\RA\2.0.8844.0\.
MSI (s) (8C:D0) [13:27:59:810]: Note: 1: 2203 2: C:\WINDOWS\Microsoft Data Protection Manager\DPM\Agents\RA\2.0.8844.0\dpmra.msi 3: -2147287037
MSI (s) (8C:D0) [13:27:59:810]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (8C:D0) [13:27:59:810]: MainEngineThread is returning 1612
-----------------------------

The agent upgrade requires the file dpmra.msi from the directory C:\WINDOWS\Microsoft Data Protection Manager\DPM\Agents\RA\2.0.8844.0\.
This is actually the installation file from the current agent version (2.0.8844). The issue is that this directory does not exist on the server and the installation files are not in any other directory on the server.

Solution (workaround)
The only way I could get the required source files was installing the old agents files (2.0.8864) to (a temporary)machine. The source is available on the DPM server (\\dpmservername\c$\Program Files\Microsoft DPM\DPM\Agents\RA\2.0.8844.0).
When installing the agent a temporary directory is created on the machine (like: 4cf3806aac3ed28e02810670b5) copy during installation the files from this directory to temp directory.
Now you have a valid copy of the installation files. Copy these installations files to the server that fails to upgrade the agent (directory C:\WINDOWS\Microsoft Data Protection Manager\DPM\Agents\RA\2.0.8844.0\) and retry the agent upgrade

Not a very nice solution, but at least it worked for me…

DPM 2007: Hotfix Rollup Package - KB979970

On March the 29th a new Hotfix rollup package for DPM 2007 has been release by Microsoft

Available here: http://support.microsoft.com/kb/979970

Information form the Microsoft website:

This hotfix rollup resolves the following issues:

1. You may experience a crash in the Data Protection Manager engine when you run a tape job from a protected server.
2. 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:

   PrmDatasetDatasourceMismatchForArchiveOfSC (=30132)

3. 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.
4. Alerts for standby continuous replication (SCR) servers are not displayed in Microsoft Operations Manager.
5. Default disk allocations may grow unexpectedly for system state protection.
6. When you restore a SharePoint site that contains a WEB host header to an alternate location, the site is restored to the default site.
7. Shared Services Provider (SSP) database protection is blocked when one or more SSP names begin with the same SSP name.
8. The server is slow, and time-out errors may occur, when you run a backup-to-tape job.
9. Data Protection Manager-owned tapes are marked as unrecognized.
10. 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:

    3103

11. You receive the following protection agent error code when bulk tape jobs cannot be completed successfully:

    0x80990C27

12. You may experience a Data Protection Manager engine crash during backup to tape.
13. 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):

Prerequisites

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

Dynamic Disk Hotfix

Quote from http://blogs.technet.com

A potential problem with Volume Manager on Windows Server 2008 systems may lead to data loss.

This hot fix is not DPM-specific.  However, because DPM servers do utilize dynamic disks, it is important to apply this hotfix on WS08-based DPM servers so that your backup-data is not lost from the DPM storage pool.

For more information please read the link below to the hot fix.

962975    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

http://support.microsoft.com/kb/962975

This hot fix does not apply to Windows Server 2008 R2

Data Protection Manager 2007 Hotfix Package KB976542

New hotfix for DPM 2007 available. More info here:

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=74ac7461-dbfe-4bc1-85a2-4d2948f30e42

New release for KB970867

Scug.be reports that Microsoft has released a new version of KB970867. More details here and on the Microsoft site

Exchange mailbox of user from other domain not showing under recoverable item

I run in to a rather strange issue with restoring mailboxes for a customer DPM implementation.
They have an Exchange 2007 SP1 CCR cluster on Windows 2008 SP2 in domain A.

The Exchange cluster is protected with a DPM SP1 server on Windows 2008 SP2 also in domain A. The Exchange server hosts mailboxes from users in many different domains but in the same forest.
The creation of recovery points works without errors and the log files are cleared as expected.
The issue is with recovering a mailbox. When selecting the recovery tab in the DPM administrative console, and select the Exchange cluster, then the storage group and then expand the mailbox store. Here under recoverable item I would expect to see all mailboxes in this mailbox store but instant we see only some of the mailboxes. Infect only the mailboxes of users located in the same domain as the Exchange server (domain A).Recovering the mailboxes is not a problem. When doing a recovery of the mailbox store to the recovery storage group all mailboxes in that mailbox store can be recovered this includes the mailboxes of users in other domains.


UPDATE: There is a hotfix rollup package for System Center Data Protection available that fixes this and 13 other issues. The hotfix number KB 968579 (thanks to Nagesh [MSFT] for pointing me in the right direction).
This also brings me to another important link: Recommended hotfixes for Microsoft Data Protection Manager 2007 systems.