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…

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