The recently released Update Rollup 3 for System Center 2012 Data Protection Manager Service Pack 1 (DPM 2012 SP1) has 2 issues that impact protected server agent upgrade and the ability to modify protection groups. In light of this discovery we have temporarily suspended availability of the update through Microsoft Update. We are actively working on fixing these issues and we will re-release the update once we have confirmed the issues listed below are addressed. Until UR3 is re-released, we encourage you to determine if you are at risk for hitting these issues by reviewing the issues/workarounds listed below.
NOTE: You will only be impacted and you only need to use the workarounds below if your DPM servers have been upgraded to System Center SP1 Update Rollup 3 for DPM (KB2852310.)
How to know if the DPM server has been upgraded to Update Rollup 3
Open the DPM Console and click the About menu option. In the dialog box check to see if the DPM version is "4.1.3415.0." If that is the version then your DPM server has been upgraded to Update Rollup 3 and you should proceed with the following workarounds.
Issues/Workarounds
Issue 1: Connected Agent Flow Issue
After applying Update Rollup 3 to the DPM server, an upgrade of protected server agents through the DPM UI using the connected agent flow fails (with id:317). This error does not affect DPM functionality. Currently there are no fixes available for this issue and no action is required by you at this time. The final fix where the connected agent install will be enabled will be released shortly.
Issue 2: Modify Protection Group Issue
After applying Update Rollup 3 to the DPM server, the modify protection group flow is broken for some of the protection groups and this will fail with Error Code 1004. Furthermore, the backup schedules for some of the protection groups also may be affected. To determine if you are impacted, run the following script to detect if any of your protection groups are affected. For some data sources, synchronization jobs run as scheduled but recovery points or tape jobs are never run. In these instances, there are no errors flagged or failed jobs indicating the problem. It is possible to manually create recovery points in order to maintain backups. Please note again: This is only applicable for DPM Servers where Update Rollup 3 was installed.
Instructions to run the script
1. Open the SQL Management Studio and connect SQL instance where the DPM database resides
2. Run the script below in SQL Query Window against the DPM database
SELECT*FROM tbl_SCH_ScheduleDefinition
WHERE IsDeleted = 0
AND
(
JobDefinitionId IN
(select JobDefinitionId from tbl_JM_JobDefinition where IsDeleted = 1 and ProtectedGroupId isnotnull)
OR
JobDefinitionId NOTIN
(select JobDefinitionId from tbl_JM_JobDefinition)
)
Results
Please call Microsoft Support and open a support incident if:
1) The above script returns rows as this may indicate that some of your protection groups have been affected.
OR
2) If you have performed ModifyPG after installing Update Rollup 3 and you are experiencing error code 1004.