none
DPM 2012 R2 UR6 Crashes on Secondary Server RRS feed

  • Question

  • I'm receiving frequent crashes on my secondary server.  After following Microsoft's advice on a DPM database corruption issue that they could not solve for several months, I reinstalled both my primary and secondary systems from scratch throwing out all backups and databases in the process.

    Even after doing that I'm having problems on the secondary where the console crashes frequently with the error below:

    Connection to the DPM service has been lost.

    Review the application event log for information about a possible service shutdown. Verify that the following services are not disabled:
                DPM
                DPM Replication Agent
                SQLAgent$MSSQLSERVER
                MSSQL$MSSQLSERVER
                Virtual Disk Service
                Volume Shadow Copy

    ID: 917

    I suspect the crashes are due to something on the back end because it looks like the console has lost communication with the back end services.  Further, many of the protection groups are not in the "OK" state at the time of the crash, and the event log has several event ID 943's present.

    I saw this post (https://social.technet.microsoft.com/Forums/en-US/acdb418a-e7b6-4d59-92af-3b43ba0f08c6/dpm-2012-r2-console-crashes-after-install-ru5-solved?forum=dataprotectionmanager), but my system is UR6 and I don't know if it is the same issue.  Further, I saw some reference to a UR5 hotfix that would not apply.

    Anyone else seeing these problems?  I'm kind of tired of fighting problems with DPM.  I don't find it to be very stable and reliable.  It requires significant daily management to keep everything working.  It should not be that way.

    Thursday, June 18, 2015 1:54 PM

Answers

  • I already have.  He discovered that for some reason, the UI did not prevent me from adding a SharePoint content DB to both a farm backup and a SQL backup.  Normally, the management console prevents me from doing that.

    I have recreated the protection groups involved to prevent duplicate protection and am now monitoring to see if that resolves the problem.  I will likely know in a few days as the crashes seemed to come and go in waves.

    • Proposed as answer by Danny Grasso Wednesday, August 17, 2016 2:02 AM
    • Marked as answer by simdoc Wednesday, August 17, 2016 2:18 AM
    Monday, June 22, 2015 3:53 PM
  • I can confirm that this was the issue for me.

    In my case the crash was caused because on the primary DPM server the database is being protected by the SharePoint application level backup and on the secondary I chose to protect at the SQL level. Apparently the UI shouldn't let you do this, which is what I've seen previously when trying to back up SQL that is already being protected by SharePoint. Previously I'd only seen this on the same server though, not in a primary/secondary DPM setup.

    • Marked as answer by simdoc Wednesday, August 17, 2016 2:17 AM
    Wednesday, August 17, 2016 12:24 AM

All replies

  • Hi Simdoc,

    Apologies for the inconvenience, we need to do some debugging to understand the issue. Can you please open a support case with Microsoft so we can collect all the required details and investigate it further.

    Please feel free to share the SR number once the case is opened so we can track it.

    Monday, June 22, 2015 3:46 PM
    Moderator
  • I already have.  He discovered that for some reason, the UI did not prevent me from adding a SharePoint content DB to both a farm backup and a SQL backup.  Normally, the management console prevents me from doing that.

    I have recreated the protection groups involved to prevent duplicate protection and am now monitoring to see if that resolves the problem.  I will likely know in a few days as the crashes seemed to come and go in waves.

    • Proposed as answer by Danny Grasso Wednesday, August 17, 2016 2:02 AM
    • Marked as answer by simdoc Wednesday, August 17, 2016 2:18 AM
    Monday, June 22, 2015 3:53 PM
  • I can confirm that this was the issue for me.

    In my case the crash was caused because on the primary DPM server the database is being protected by the SharePoint application level backup and on the secondary I chose to protect at the SQL level. Apparently the UI shouldn't let you do this, which is what I've seen previously when trying to back up SQL that is already being protected by SharePoint. Previously I'd only seen this on the same server though, not in a primary/secondary DPM setup.

    • Marked as answer by simdoc Wednesday, August 17, 2016 2:17 AM
    Wednesday, August 17, 2016 12:24 AM