none
DPM 2010 protecting Sharepoint 2010 - Backup metadata enumeration failed RRS feed

  • Question

  • Hi

    I am using DPM 2010 to protect SharePOint 2010 Ent farm. I run through configuration files and everything installed succesfully.

    After i run backup, i get success message followed by this error

    Status: Backup metadata enumeration failed
    Replica path: Click to view details

    How to troubleshoot this problem?

    (previous question removed)

    Thanks

    • Edited by Damir Tejic Monday, December 13, 2010 10:59 AM
    • Moved by MarcReynolds Tuesday, December 14, 2010 12:55 PM (From:Data Protection Manager)
    Monday, December 13, 2010 9:49 AM

All replies

  • Hi Damir,

                There is a lot of nice features you can use with DPM 2010 based on your needs so as you already backed up the Sharepoint and its related SQL databases you have options either to protect the system state of your servers in order to protect the Operating system or even using BMR to backup the entire server.

    using DPM you can backup :

    - System State
    - SQL
    - Exchange Servers
    - Virtualization with Microsoft Hyper-V
    - Files in Servers and Clients
    - BMR (Bare Metal Backup)
    - Self Service Recovery for SQL

    and Item Level Recovery in both Hyper-V and Sharepoint.

    please refer to the following for more Info

    Exchange - http://technet.microsoft.com/en-us/library/ff399297.aspx
    SQL - http://technet.microsoft.com/en-us/library/ff399300.aspx
    Hyper-V - http://technet.microsoft.com/en-us/library/ff399446.aspx
    System State and BMR - http://technet.microsoft.com/en-us/library/ff399494.aspx
    File Servers - http://technet.microsoft.com/en-us/library/ff399373.aspx
    Client Computers - http://technet.microsoft.com/en-us/library/ff399256.aspx

    For any furthur question please let me know, hope we could help you

    Regards

    Monday, December 13, 2010 10:36 AM
  • Hi Damir,

    I ran into the same warning once "Backup metadata enumeration failed" when backing up a SharePoint 2010 WFE.

    You farm is still being backed up but you do not get item level restore until you resolve this warning.

    You need to configure a MetaData service application on the SharePoint WFE. This will fix your issue.

    This article here will explain more about what the MetaData service is and how to configure it: http://sharepointgeorge.com/2010/configuring-managed-metadata-service-application-sharepoint-2010-part1/ .

    Here is an article with more information about the MetaData Service: http://technet.microsoft.com/en-us/library/ee424403.aspx .

    Please update us after you have tried it.

    Tuesday, December 14, 2010 5:35 AM
    Moderator
  • Hi BuchaTech

    I will let you know how it went.

    "You farm is still being backed up but you do not get item level restore until you resolve this warning." this is making me feel bit better.

    Cheers

    Wednesday, December 15, 2010 8:41 AM
  • Hi Damir,

     

    Did that resolve your issue?

    Thursday, December 30, 2010 6:24 AM
    Moderator
  • No.. Still the same. I was away, so i didn't do much. Back to work now...

    Thursday, January 20, 2011 1:26 AM
  • Hi Damir,

    So were you able to configure the MetaData service application without any issues?

    Thursday, January 20, 2011 7:39 AM
    Moderator
  • Damir

    The backup metadata error occurs when DPM is unable to get the sharepoint metadata information from the Sharepoint Writer. Please see the application event logs to check for any VSS error events being thrown and paste the error here.

     

    Roopesh

    This posting is provided "AS IS" with no warranties, and confers no rights

    Friday, February 11, 2011 9:02 AM
    Moderator
  • Don't know if this is already resolved, but here is the solution for the problem:

    In Registry, you should find the following key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0\Search\Setup\ContentIndexCommon\Filters\Extension

    14.0 is the version which equals sharepoint 2010

    However, you should also find the following key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\

    Therefore, DPM thinks that sharepoint 2003 installed, which is a different logic as sharepoint 2010 and therefore DPM fails in doing the metadata enumeration.

    The solution is to export the key and delete it so that DPM knows what to do.  However, depending on the add-ins that are installed, this could cause issues for the add-ins.  My experience is that with default installed sharepoint sites (read, no 3rd party add-ins) this solution works perfectly and doesn't break the sharepoint

    Just my 2 cents,

    Cheers,

    Mike

     


    Visit System Center User Group Belgium @ http://scug.be and http://scug.be/blogs/scdpm
    Monday, July 18, 2011 4:35 PM
    Moderator
  • Don't know if this is already resolved, but here is the solution for the problem:

    In Registry, you should find the following key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0\Search\Setup\ContentIndexCommon\Filters\Extension

    14.0 is the version which equals sharepoint 2010

    However, you should also find the following key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\

    Therefore, DPM thinks that sharepoint 2003 installed, which is a different logic as sharepoint 2010 and therefore DPM fails in doing the metadata enumeration.

    The solution is to export the key and delete it so that DPM knows what to do.  However, depending on the add-ins that are installed, this could cause issues for the add-ins.  My experience is that with default installed sharepoint sites (read, no 3rd party add-ins) this solution works perfectly and doesn't break the sharepoint

    Just my 2 cents,

    Cheers,

    Mike

     


    Visit System Center User Group Belgium @ http://scug.be and http://scug.be/blogs/scdpm

    Hi Mike,

     

    Thanks for the update on this. Can you tell me if this is caused by SharePoint being upgraded from older versions to 2010?


    My Blog | www.buchatech.com | www.systemcenterdataprotectionmanager.com
    Monday, July 18, 2011 4:41 PM
    Moderator
  • Hey Steve,

    Nope,

    This even occurs when you install a fresh sharepoint 2010 foundation (for example, under the SBS).  However, when I installed sharepoint server 2010, I didn't had the issue.

    Cheers,

    Mike


    Visit System Center User Group Belgium @ http://scug.be and http://scug.be/blogs/scdpm
    Monday, July 18, 2011 4:47 PM
    Moderator
  • Hey Steve,

    Nope,

    This even occurs when you install a fresh sharepoint 2010 foundation (for example, under the SBS).  However, when I installed sharepoint server 2010, I didn't had the issue.

    Cheers,

    Mike


    Visit System Center User Group Belgium @ http://scug.be and http://scug.be/blogs/scdpm

    Hi Mike,

     

    Thanks for the clarification. I am going to ping some SharePoint gurus and see if they know why that is automatically added into the registry settings.


    My Blog | www.buchatech.com | www.systemcenterdataprotectionmanager.com
    Monday, July 18, 2011 4:53 PM
    Moderator
  • Hi Mike,

    I have a Foundation server with this error. It does not have the 12.0 reg key and there is no MetaData service application in Foundtation.

    Have you seen that before?


    My Blog | www.buchatech.com | www.systemcenterdataprotectionmanager.com
    Tuesday, July 19, 2011 5:32 PM
    Moderator
  • Hey Steve, Yes, But then the Sharepoint VSS writer got into issues. Rerunning the sharepointconfig command fixed that Cheers Mike
    Visit System Center User Group Belgium @ http://scug.be and http://scug.be/blogs/scdpm
    Wednesday, July 20, 2011 6:28 AM
    Moderator
  • Hey Steve, Yes, But then the Sharepoint VSS writer got into issues. Rerunning the sharepointconfig command fixed that Cheers Mike
    Visit System Center User Group Belgium @ http://scug.be and http://scug.be/blogs/scdpm


    Hi Mike,

    That fixed it on my Foundation farm. Thanks.


    My Blog | www.buchatech.com | www.systemcenterdataprotectionmanager.com
    Tuesday, July 26, 2011 3:47 PM
    Moderator
  • Hi

    i also had this problem with sp2010 and dpm2010.

    i had the registry 12.0.

    just check the registry key to se which program or process uses it.

    for me it was the TIFF filter.

    i had removed it and run the configuresharepint and now all is ok for me.

     

    thanks. 

    Regards,

    Uroš Zohil

    • Edited by Uros Zohil Friday, September 6, 2013 7:44 AM
    Thursday, September 1, 2011 12:28 PM