none
DPM 2012 Backup Sharepoint 2007 error RRS feed

  • Question

  • Hi. Whenever I try to backup our Sharepoint 2007 Server, an error appears in the SQL and the backup Fails.

    Source: SQLWRITER
    EventID: 24583
    Description: Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 5198
    Error state: 1, Severity: 16
    Source: Microsoft SQL Native Client
    Error message: The path specified by "\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy88\....." is a UNC path. UNC path is not supported in failover clustered enviornment.

    With DPM 2010 we have no issue. The problem started when I migrate to the 2012 version of DPM.

    DPM Server 2012
    Sharepoint 2007 with SQL 2005 in Cluster

    How can I solve this issue?

    Thanks in advice.

    Friday, June 29, 2012 4:33 PM

All replies

  • Hi,

    This is a problem currently under investigation, however it is caused by DPM 2012 taking auto-recoverable snapshots which allows for optimized sharepoint recoveries. The problem is SQL 2005 does not support auto-recoverable snapshots when running on a cluster.

    Only solutions at the moment are:

    A) Continue to use DPM 2010 to protect that clustered farm.
    B) Upgrade the farm to use SQL 2008.
    C) Don't use Clustering.

    Otherwise, we will need to wait and see if this is something we can address in a DPM change, but that might take awhile.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, July 11, 2012 2:02 AM
    Moderator
  • Having the same issue.

    wondering if I can Backup all the sharepoint files, separately. Maybe not 100%. but still better then having nothing to restore.

    Greetings,

    Friday, July 13, 2012 5:23 PM
  • Hi, 

    is this issue solved by any KB ? or in DPM 2012 R2 ?

    Monday, May 5, 2014 11:46 AM
  • Hi,

    The issue was investigated and the issue is in the SQL 2005 writer.  This is fixed in later versions of SQL server and there are no plans to back port the fix, so the guidance would be to move to SQL 2008.  There are no DPM updates to get past the limitations of the SQL 2005 writer.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, May 5, 2014 3:37 PM
    Moderator
  • Thanks Mike for your reply,

    for DPM 2012 R2 RollUp 2 , its stated that it's supported as below, can you confirm on that ?

    "The following workloads are supported on Win2K3:

    • SQL 2005
    • SQL 2008
    • SQL 2008 R2
    • SharePoint 2007

    UR2 also adds support for protection of availability groups built over clustered SQL instances."

    http://blogs.technet.com/b/dpm/archive/2014/04/23/now-available-update-rollup-2-for-system-center-2012-r2-data-protection-manager.aspx 

    Wednesday, May 7, 2014 7:30 AM
  • Hi,

    Yes, that is correct information, however UR2 was pulled due to a regression.  Will be re-released later in the month.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, May 7, 2014 5:53 PM
    Moderator
  • Hi mike, Rollup is now published i just need confirmation that we can backup with DPM 2012 r2 rollup2 sharepoint 2007 with backend SQL cluster 2005 on windows 2003
    Wednesday, May 21, 2014 2:53 PM
  • Hi,

    DPM 2012 + cannot protect a sharepoint farm when SQL 2005 is clustered. 

    The issue was investigated and the issue is in the SQL 2005 writer.  This is fixed in later versions of SQL server and there are no plans to back port the fix, so the guidance would be to move to SQL 2008.  There are no DPM updates to get past the limitations of the SQL 2005 writer.

    Only solutions at the moment are:

    A) Continue to use DPM 2010 to protect that clustered farm.
    B) Upgrade the farm to use SQL 2008.
    C) Don't use Clustering.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    • Proposed as answer by Mina Fouad Wednesday, June 18, 2014 12:17 PM
    Wednesday, May 21, 2014 3:58 PM
    Moderator