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.
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.)
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.
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.
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
( select JobDefinitionId from tbl_JM_JobDefinition where IsDeleted = 1 and ProtectedGroupId is not null)
JobDefinitionId NOT IN
( select JobDefinitionId from tbl_JM_JobDefinition)
The System Center 2012 SP1 UR3 package for DPM was re-released on 8-20-13 and fixes the above two issues. You can simply install the new UR3 re-released package available here:
KB2877075 - Rollup 3 for System Center 2012 SP1 - Data Protection Manager (http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2877075)
The new DPM version will be 4.1.3417.0 after applying this update.
This update is timely removed from public. But I really need it. Thanks for the suggestions.
Would be helpful if they published some uninstall guidelines. Presume i can just uninstall it from the 'installed updates' but don't want to break a production DPM server, so not happy to do it without advise from MS.
I'm catch it :(
We have 15 affected rows and get error 1004 when we try to modify a protection group. Not sure whether we want to open a support incident or just wait for a general fix. Has anyone called technical support yet, and how much time was involved?
8 affected rows here, cant modify protection groups either. Looked into giving MS a call, but what a pain.
same here... some are working... some not. Also can't delete a group member...
Anyway to get notified when the fix is available?
Case opened, but the support engineer doesn't seem to know much about this either and need to wait for the response from DPM dev team. :(
Can someone provide the link to open a free support case? on the phone, they're trying to charge the support call.
Support helped me to fix issues. Since it's a product bug, it's free of charge. And related scripts (sql script to delete orphan entries, powershell script to regenerate job definitions) are not allowed to provide.
So you guys just go ahead and ask for help. :)
@Alex Ieong Same with me. Just had my support call. DPM seems to be fixed now (except the agent update issue).
I was told to not share the scripts. If you have this issue open a case, it is free of charge.
You guys are lucky, I called the Belgian Support and the person taught I was calling for hotfix KB2853210 and kept telling me the kb doesn't exist.
I'll try again :)
Dear fellows, Belgian Support keeps asking for a hotfix number, but I only have the KB number that I installed the update (KB2852310) can someone @Microsoft check this please, I'm loosing patience here :(
@Sami Just show your regional support this blog entry and SQL query result. No more nonsense, right? :)
@Alex, I ended up opening a case via the online support with one of my incident support :)
I don't blame the person, but they didn't have technical knowledge to be enough helpful to redirect me to a 2nd level or more advanced tech. I'm waiting here that support contact me back with the solution.
Just finished the support call with Microsoft. Very quick and professional, and all is now well. No charge. No fuss.