none
DPM 2012 SP1 Update Rollup 1 failing to backup Sharepoint 2010 PG + other SP databases RRS feed

  • Question

  • Hi guys

    Environment

    I have recently upgraded from DPM 2010 to DPM 2012 SP1 running on 2008 R2 SP1. I also have:

    A Sharepoint 2010 farm running on Server 2008 R2 SP1 Hyper-V machine using a SQL 2008 R2 (10.50.2861) backend.

    DPM server: DPM.contoso.info

    SQL server: SERVER.contoso.info

    Problems

    After upgrading from DPM 2012 to DPM 2012 SP1 I began having a few issues, mainly:

    1. DPM won't backup Server 2012 virtual machines with child partition, but instead uses saved state.
    2. DPM won't backup 4 SQL databases associated with Sharepoint 2010 and the Sharepoint protection group itself fails.

    Just to clarify, before applying SP1 I didn't have any of these problems.

    1. DPM won't backup Server 2012 virtual machines with child partition, but instead uses saved state.

    I will only touch on this real quick but I have a few Server 2012 Hyper-V VM's running on a Server 2008 R2 Hyper-V CSV failover cluster, I have updated the DPM agent on the cluster after applying Update Rollup 1. No hardware vss providers are in use and all Server 2008 R2 machines are backed up with child partition flawlessly.

    I was expecting that with upgrading DPM 2012 to SP1 I would be able to backup these VMs as child partition as opposed to saved state. None of these VM's were backed up with DPM in the past, I waited until running SP1 before adding them to DPM.

    Any suggestions or clarifications on this one would be helpful.

    2. DPM won't backup 4 SQL databases associated with Sharepoint 2010 and the Sharepoint protection group itself fails.

    I am backing up Sharepoint 2010 itself with a Sharepoint Protection Group plus some extra SQL databases that SP uses through my standard SQL protection group.

    The 5 problematic databases all complain that:

    DPM could not run the backup/recovery job for the data source because it is owned by a different DPM server.
    Data source: SERVER\Managed Metadata Service_ee5e29e51d4042fca2bac06737080374
    Owner DPM Server: . (ID 3184 Details: The file or directory is corrupted and unreadable (0x80070570))

    There has hasn't been another DPM server in our environment since DPM 2007 and that server has never backed up the databases that are complaining of being owned by another DPM server.

    The 5 databases affected are:

    SERVER\Managed Metadata Service_ee5e29e51d4042fca2bac06737080374

    SERVER\Bdc_Service_DB_9d819dfe837c43b68750c25595bad1c9

    SERVER\Application_Registry_Service_DB_e46f9a269fb3484e9ad74c985793fed5

    SERVER\PerformancePoint Service Application_5e0c3b3054cb4f359739b22bb2765e85

    And the 5th database appears when I click on the "View Detailed Errors" of the Sharepoint protection group it says:

    DPM could not run the backup/recovery job for the data source because it is owned by a different DPM server.

    Data Source: SERVER\SharePoint_AdminContent_41979eaf-67b4-4769-b86e-fa703644f2fb

    Owner DPM Server: . (ID 3184 Details: The file or directory is corrupted and unreadable (0x80070570))

    So "SERVER\SharePoint_AdminContent_41979eaf-67b4-4769-b86e-fa703644f2fb" is the 5th database effected.

    Attempted Fixes

    I have tried using the DPM's suggestion of "take data source ownership" but it is not working, logs don't indicate any success or failure.

    I am also backing up other SQL databases on the same server AND other sharepoint sql databases on the same server, so its only these 5 databases affected.

    I have trawled through logs, events and permissions and I can't find anything wrong. I am wondering if there is something that I am missing, or if this is a SP1 or Update Rollup 1 issue.

    Attached Logs

    I have attached below the output of the MSDPMCurr.errlog when I trigger a synchronization job of the Application_Registry database. I have replaced my domain and server names consistently in the logs.

    Due to body size restrictions I have pasted the log contents into a pastebin available here >> http://pastebin.com/FHEbnr6W




    • Edited by youngpro Thursday, January 17, 2013 2:12 AM
    Thursday, January 17, 2013 2:11 AM

All replies

  • Problems

    After upgrading from DPM 2012 to DPM 2012 SP1 I began having a few issues, mainly:

    1. DPM won't backup Server 2012 virtual machines with child partition, but instead uses saved state.

    You are not alone.  I have the same issue here. But no solution.

    Did anybody test it with DPM 2012 SP1 installed on Windows Server 2012?

    Wednesday, January 23, 2013 2:08 PM
  • Hi,

    in our test environemnt I use Windows 2012 and SCDPM SP1 RC version to backup our Test SharePoint Farm 2010. That works but I have not done an upgrade from DPM 2012 to DPM 2012 SP1 nor an upgarde from Windows 2008 r2 to windows 2012. So in generall it should work.

    Wednesday, January 23, 2013 3:18 PM
  • You are not alone.  I have the same issue here. But no solution.

    Did anybody test it with DPM 2012 SP1 installed on Windows Server 2012?

    This is what I am also wondering, must DPM itself or the Hyper-V machine itself be on Server 2012 to successfully backup 2012 VM's with child state.

    Thursday, January 24, 2013 12:02 AM
  • After some testing I can say, that DPM 2012 SP1 on Windows 2012 also can not backup Windows 2012 VMs in a Windows 2008 R2 Hyper-V Cluster online.

    But it is possible to backup Windows 2012 VMs in a Windows 2012 Hyper-V Cluster online.

    But I could not find anything about the fact that the first option is not supported.

    Thursday, January 24, 2013 7:57 AM
  • I just wanted to note that my SharePoint 2010 databases all seem to backup fine with DPM 2012 SP1, but I do have the issue where I can't backup 2012 VMs online whether they are in a 2008 R2 cluster, or a 2008 R2 stand-alone host. I assume this means that the Hyper-V hosts (clustered or not) have to be upgraded to Server 2012 in order to allow DPM 2012 to backup the VMs online. I can't find documentation to support this.

    On the SharePoint issue; this is probably a silly suggestion, but have you  re-installed your agents, and re-run the "ConfigureSharepoint.exe -enablesharepointprotection"?

    Friday, February 1, 2013 4:57 PM
  • Hi,

    I can confirm that Windows 2012 guests NOT running on a Windows 2012 Hyper-v host will go into a saved state when any backup application using VSS shadow copies does a backup of that guest.  This is not a DPM issue, it has to do with integration component Incompabilities between windows 2012 guest and a down level hyper-v host. . Solution is to upgrade the hyper-v server to Windows 2012.

    As for the SharePoint issue, I have not heard of any SharePoint protection issues with DPM 2012 SP1.


    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, February 4, 2013 6:02 AM
    Moderator
  • 2. DPM won't backup 4 SQL databases associated with Sharepoint 2010 and the Sharepoint protection group itself fails.

    I am backing up Sharepoint 2010 itself with a Sharepoint Protection Group plus some extra SQL databases that SP uses through my standard SQL protection group.

    The 5 problematic databases all complain that:

    DPM could not run the backup/recovery job for the data source because it is owned by a different DPM server.
    Data source: SERVER\Managed Metadata Service_ee5e29e51d4042fca2bac06737080374
    Owner DPM Server: . (ID 3184 Details: The file or directory is corrupted and unreadable (0x80070570))

    There has hasn't been another DPM server in our environment since DPM 2007 and that server has never backed up the databases that are complaining of being owned by another DPM server.

    The 5 databases affected are:

    SERVER\Managed Metadata Service_ee5e29e51d4042fca2bac06737080374

    SERVER\Bdc_Service_DB_9d819dfe837c43b68750c25595bad1c9

    SERVER\Application_Registry_Service_DB_e46f9a269fb3484e9ad74c985793fed5

    SERVER\PerformancePoint Service Application_5e0c3b3054cb4f359739b22bb2765e85

    And the 5th database appears when I click on the "View Detailed Errors" of the Sharepoint protection group it says:

    DPM could not run the backup/recovery job for the data source because it is owned by a different DPM server.

    Data Source: SERVER\SharePoint_AdminContent_41979eaf-67b4-4769-b86e-fa703644f2fb

    Owner DPM Server: . (ID 3184 Details: The file or directory is corrupted and unreadable (0x80070570))

    So "SERVER\SharePoint_AdminContent_41979eaf-67b4-4769-b86e-fa703644f2fb" is the 5th database effected.




    Hi,

    I am experiencing the same issue on DPM 2012 R2 UR2.

    I have found a temporary fix on this page:

    http://blog.metasplo.it/2013/04/dpm-2012-sp1-replica-inconsistent.html

    1. Open  "c:\program files\Microsoft Data Protection Manage\dpm\activeowner" on the database server. 

    2. Rename any 0 KB files to <name>.old 
    3. Run SetDpmServer from ""c:\program files\Microsoft Data Protection Manage\dpm\bin"Syntax: SetDpmServer.exe -DpmServerName <SERVER>
    Replace server with the computer name of your DPM server. 
    4. Re-run your synchronization
    This is a good solution, but I have to do this everiday, which is not exeptable.

    Has anybody found a solution to this problem?

    Wednesday, May 6, 2015 5:51 AM
  • Hello.

     

    I had completed the tasks shown, however the issue wasn’t resolved in the infrastructure given.

     

    In my end just a sharepoint database had this issue:

     

    * SERVER_Sharepoint \ SharePoint_AdminContent_8145af4b-3010-4ed3-9a18-2e36a2b93ce5.mdf

     

    Below you will find the reference that allow me to solve my problem, I only performed some additional steps:

     

    1. Stop protection of the database from the console of scdpm 2012 R2

     

    2. Remove the replicas of the database stored on the disk.

     

    3. Rename the file to the following location: 

     

    "C: \ Program Files \ Microsoft Data Protection Manager \ DPM \ ActiveOwner \ OVRTK-SP13 + SharePoint_AdminContent_8145af4b-3010-4ed3-9a18-2e36a2b93ce5"

     

    to

     

    "C: \ Program Files \ Microsoft Data Protection Manager \ DPM \ ActiveOwner \ OVRTK-SP13 + SharePoint_AdminContent_8145af4b-3010-4ed3-9a18-2e36a2b93ce5.bak "

     

    3. Add the database back to the protection group.

     

    4. Run manually the first replica of  database from the management console scdpm 2012 R2.

     

    5. As validation you will see the newly generated files with  a measure of 1KB.

    Friday, February 12, 2016 4:40 AM
  • Hello.

     

    I had completed the tasks shown, however the issue wasn’t resolved in the infrastructure given.

     

    In my end just a sharepoint database had this issue:

     

    * SERVER_Sharepoint \ SharePoint_AdminContent_8145af4b-3010-4ed3-9a18-2e36a2b93ce5.mdf

     

    Below you will find the reference that allow me to solve my problem, I only performed some additional steps:

     

    1. Stop protection of the database from the console of scdpm 2012 R2

     

    2. Remove the replicas of the database stored on the disk.

     

    3. Rename the file to the following location: 

     

    "C: \ Program Files \ Microsoft Data Protection Manager \ DPM \ ActiveOwner \ OVRTK-SP13 + SharePoint_AdminContent_8145af4b-3010-4ed3-9a18-2e36a2b93ce5"

     

    to

     

    "C: \ Program Files \ Microsoft Data Protection Manager \ DPM \ ActiveOwner \ OVRTK-SP13 + SharePoint_AdminContent_8145af4b-3010-4ed3-9a18-2e36a2b93ce5.bak "

     

    3. Add the database back to the protection group.

     

    4. Run manually the first replica of  database from the management console scdpm 2012 R2.

     

    5. As validation you will see the newly generated files with  a measure of 1KB.

    I'm having a similar issue here  which i think is the same (except ours is sharepoint 2013).. is this the only way to correct this.. does this corrupted and unreadable mean that the dpm server is the corruption point?  Is there no way to correct this while maintaining data history, in our case the last 30 days.. deleting and recreating obviously would wipe that.   

    And attempting to remove the pg (one or all) just sits there in progress, never removes.


    Tech, the Universe, Everything: http://tech-stew.com Just Plane Crazy http://flight-stew.com

    edit:  for the activeowner in step 3, i dont even see those files either locally on the dpm server or on the remotely protected ones.. similar files though..

    These seem to be on the remotely protected sql server.. all the ones that say sp2k13 in my case.. so i assume those need deleted.


    • Edited by techfun89 Tuesday, January 31, 2017 6:32 PM
    Tuesday, January 31, 2017 3:21 PM