none
SharePoint Catalog Task RRS feed

  • Question

  • Hi,

    I am using DPM 2012 and it is working perfectly fine but my “SharePoint Catalog Task” keeps running for couple of day and more.  If anyone can help me out to resolve this issue will be highly appreciated.

    Note: Windows Update and DPM 2012 is up-to-date.

    Thanks & regards,

     


    MD Disclaimer: The opinion expressed herein are my own knowledge. Deploy this at your own risk. Whenever you see a helpful reply, just click on “Propose As Answer” / “Marked As Answer” and please do "VOTE".

    Sunday, September 29, 2013 11:29 AM

Answers

  • Hi,

    1. Open REGEDIT in SharePoint Server

    2. Go to the following Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent\2.0\

    And set NumberOfCatalogThreads to "3"

    For this to have effect, Restart "DPMRA"service 

    =============================

    Dear All,

    "SharePoint Catalog Task" issue has been resolved after upgrading our "DPM 2012" to "DPM 2012 R2"

    Regards,



    MD Disclaimer: The opinion expressed herein are my own knowledge. Deploy this at your own risk. Whenever you see a helpful reply, just click on “Propose As Answer” / “Marked As Answer” and please do "VOTE".



    Monday, December 30, 2013 5:39 AM

All replies

  • Hi,

    1. Open REGEDIT in SharePoint Server

    2. Go to the following Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent\2.0\

    And set NumberOfCatalogThreads to "3"

    For this to have effect, Restart "DPMRA"service 

    =============================

    Dear All,

    "SharePoint Catalog Task" issue has been resolved after upgrading our "DPM 2012" to "DPM 2012 R2"

    Regards,



    MD Disclaimer: The opinion expressed herein are my own knowledge. Deploy this at your own risk. Whenever you see a helpful reply, just click on “Propose As Answer” / “Marked As Answer” and please do "VOTE".



    Monday, December 30, 2013 5:39 AM
  • Hi,

    I'll try to guess what's happening on the WFE side. Set the DPM logs to verbose on the WFE, restart the agent, launch a catalog creation on DPM PowerShell, and look at the CmdletWrappersCurrent.log file in the WFE, where the agent goes contentdb by contentdb creating the catalogs (it is quite verbose as it gives a lot of detail). This way you can get to know whether the indexaton it is simply very slow or if the agent is stuck somewhere. do you have many content databases?

    If you have a large farm with a very big number of items, then the problem could be in the DPM database. You should reorganize/recreate indexes on the table that stores the catalog:

    http://technet.microsoft.com/en-us/library/ff399024.aspx

    HTH

    Roberto

    Friday, January 10, 2014 1:55 PM