Important Update on DPM 2012 SP1 Update Rollup 3–Issues and Workarounds (Update: UR3 has been re-released) - The Official System Center Data Protection Manager Team Blog - Site Home - TechNet Blogs

Important Update on DPM 2012 SP1 Update Rollup 3–Issues and Workarounds (Update: UR3 has been re-released)

Important Update on DPM 2012 SP1 Update Rollup 3–Issues and Workarounds (Update: UR3 has been re-released)

  • Comments 36
  • Likes

ImportantThe 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.)

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. 

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 =

AND

(

  JobDefinitionId  IN

   ( select JobDefinitionId from tbl_JM_JobDefinition where IsDeleted = 1 and ProtectedGroupId is not null)

  OR

  JobDefinitionId NOT IN

   ( select JobDefinitionId from tbl_JM_JobDefinition)

)

Results

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.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Hello,

    despite the fact I've seen the alert on this *buggy* RU, it has been installed anyway. :-(

    I have 41 lines in the SQL result, that may correspond to all my tape backups that haven't been triggered.

    I'm opening a support ticket at Microsoft France to fix this issue. I should be contacted back within4 hours (urgent ticket).

  • Hi everyone, sorry about the confusion. Please reference ID number 2877069 when opening your case. This will expedite resolution of your issue.

  • I got in touch with Microsoft France Support engineer. He sent me the 2 scripts some of you talked about:

      1. RevertBackGCAndDeleteSchedule.sql.txt  (For SQL Management Studio)

      2. RegenerateJobDefsTranslateDS_WithoutDDC.ps1 (For DPM'ed PowerShell)

    Along with those 2 scripts, a quite straight forward procedure with pre-requisistes checks, actions, and final check.

    The procedure just took about 3-4 minutes to complete. Every thing seems to be fine.

    I'll check tomorrow if all my Protections Groups will get back to *green*, with this night latest Recovery Point.

    Pascal.

  • Hi,

    the German support was not able to help. They couldn´t find the reference ID number 2877069 in their database. Could someone give me an schedule when the official hot-fix will be available.

  • All is OK after the procedure to fix the bug.

    Pascal.

  • I started off querying the database and received 22 rows from the query. I removed and recreated one of my protection groups, then modified it and added another data source to it successfully. After that I ran the query again, and it still returned 22 rows, but I was then able to modify the protection group since it was recreated. So while that is a workaround it does not fix the database issues.

    I will call MSFT for the SQL and PowerShell script today to clean up my database entries and fix the rest of my protection groups.

  • Backup software has been out for over 20 years now. Windows NTBackup came out heck when NT3 came out or maybe it was version 4. But in any event there was plenty of products out there and lessons learned to see what did and didn't work. (As well as numerous forum responses and user requests over the years) So my question to Microsoft and the DPM team is why didn't you guys take any of this stuff and put out a polished and finished product? I'm going to ruffle feathers here but this needs to be asked. This product was not a finished product when it first came out and 2012 SP1, or R2 is not either.  WHY?

    AS a Microsoft User going back to when you guys first came out I think we are ALL owed an answer.

    Ever since Balmer took over this company has gone into the toilet fast. If the goal is to drive your company into the ground then let us know so we can leave and go to Linux or Unix or dare I say it, crapple...

    Come on guys and gals what in the heck is going on?  

    What in the heck were you thinking with the whole tape thing? COME ON! WHY IN THE HECK CAN I NOT SAVE LONG TERM TO DISK! WHY AM I FORCED TO GET A 3RD PARTY PROGRAM ACTING AS A VTL TO SAVE LONG TERM!! WHO THE HECK IS RUNNING THINGS AT MICROSOFT???

  • I have one Fileserver doesn't create recovery Points scheduled and an Exchange Server with the same Problem.

    The Exchange Databases on the same server working as usual.

    I have 10 rows they seems to be affected and trying to contact the german Support 2mrw.

    Hopefully the can help me.

    I'll give a Feedback asap. :)

  • Microsoft Support in Australia was of no help with this issue. Firstly, despite quoting the above reference ID the support person was unable to find the issue. Then when she did contact me a few hours later and it appeared she had found this blog article and said I would need to lodge a paid support job to get the fixes for this issue. Not happy! Now nearly 2 weeks without a fully functional backup.

  • I'm glad that microsoft changed their support system in france, between the girl that answer and almost tell you to GFY and do a web request and the web site that doesnt work to get new request, i'm over happy that my DPM is now broken :/

  • German support said they know about the reference ID the problem is known and they can help me. Scheduled for 2mrw and it involves a powershell script and a sql query.

  • Yeah I had the same issue and initially had some resistance when logging the fault mainly due to them not wanting to log it unless I had valid support details. Finally they accepted our licence agreement details as proof (an agreement that covers 30 large organisations, I dread to think how much we are paying MS!!)

    When I finally got one of their senior system center guys on the case he was pretty good and had the problem fixed with a couple of scripts (SQL and powershell). It was quite amusing when he tried to run the powershell script though, it kept giving an error (wouldn't allow an unsigned script to run which is the default security setting on Server 2K12). He kept repeating, this has worked on all the other servers I have fixed, and I kept telling him the security settings would need temporarily relaxing ... I took control and sorted it in the end, he was in full headless chicken mode at that point ...

  • German Support (located in romania) worked that out within half an hour. Most of the time preparing, downloading, chattering etc.

    At the end it's working as described before.

    They have a similiar SQL Query which shows the affected rows and a powershell script what fixes the Problem.

    Note:

    If someone get Troubles...

    I had have one DPM Server with an underlined Database Name (DPM_Server_Name_Number) and that is not supported for DPM.

    The PowerShell Script from the support won't work if it is directly executed but is working inside the DPM PowerShell cmd.

    Unfortunatley I had to delete the scripts because they restricted for internal use only.

    But they don't charge the call or counting it from your VL SA accounts.

  • any updates on the rerelease of UR3?

    Regards,

    Peter

  • This morning, an update shown up my DPM 2012 SP1 server... maybe the new version to replace the the buggy Update Rollup 3 released in July (KB2852310)

    Update Rollup 3 for System Center 2012 SP1 - Data Protection Manager (KB2877075)

    Download size: 409,6 MB

    Update type: Important

    This update fixes the problems described in KB article 2836751 .

    On Microsoft update Catalog, it says that it superseeds the buggy KB2852310.

    Check: catalog.update.microsoft.com/.../Search.aspx

    This time, I will wait until Microsoft Team communicate on this release before applying it.

    KB2008095 = DPM 4.1.3333.0

    KB2822782 = DPM 4.1.3408.0

    KB2853210 = DPM 4.1.3415.0

    KB2877075 = DPM 4.1.3417.0 (from a manual extraction of the downloaded package)