locked
Mergecontentdbs Fails on Large Site Collections RRS feed

  • Question

  • Hello all,

    I am trying to move some site collections to a new Content Database, but it fails without providing an error. This typically happens on Site Collections that are 8 GB and larger. I am using the mergecontentdbs stsadm command. Any clues? Does anyone have documented limits on moving Site Collections/recommendations? Any third party tools worth noting?

    Thanks,

    Kelly


    Personal Blog: http://thebitsthatbyte.com

    Tuesday, November 6, 2012 3:45 AM

All replies

  • Hi Kelly,

    First, make sure you have Full Control permission on the site collection that needs to be move. Then check free space on your driver, it is recommended that the available free space is at least three times the size of the source site collection. If there is not so much free space, better to clean your driver first.

    You may also check the Remarks for the Mergecontentdbs command from the following reference.
    http://technet.microsoft.com/en-us/library/cc262923(v=office.12).aspx

    Also check if there is any error in your ULS log and SQL Server transaction logs.

    Thanks & Regards,
    Emir Liu
    TechNet Subscriber Support in forum
    If you have any feedback on our support, please contact tnmff@microsoft.com.


    Emir Liu

    TechNet Community Support

    Wednesday, November 7, 2012 6:14 AM
  • Thanks Emir, to clarify the free space. Is that free space on the SQL drive? I don't see why the Web Front
    End would need the space since the data is not stored there.

    Personal Blog: http://thebitsthatbyte.com

    Wednesday, November 7, 2012 6:01 PM
  • Hi Kelly,

    Yes, please check your driver on SQL Server.

    Thanks & Regards,
    Emir


    Emir Liu

    TechNet Community Support

    Thursday, November 8, 2012 5:56 AM
  • Thanks Emir,

    The data drive has plenty of space. At least 3 times the size of the site collection.

    Regards,

    Kelly


    Personal Blog: http://thebitsthatbyte.com

    Thursday, November 8, 2012 2:11 PM
  • Hi Kelly,

    Thanks for your reply.

    Have you checked ULS log and SQL log, is there any error there?

    Thanks & Regards,
    Emir


    Emir Liu

    TechNet Community Support

    Friday, November 9, 2012 2:50 AM
  • Hi Emir,

    None that appears to show, but I will dig deeper. Are you aware of size limits for moving a site collection? Do you have any third party tool recommendations if the site collection is, perhaps, 15 GB or larger?

    Thanks,

    Kelly


    Personal Blog: http://thebitsthatbyte.com

    Friday, November 9, 2012 3:43 AM
  • Hello Kelly,

    Under certain circumstances STSADM MergeContentDBs command may fail or may cause database corruption. More details are available at http://support.microsoft.com/kb/969242.

    You may want to try the "Batch Site Manager" tool which is available as a part of SharePoint Administration Toolkit.
    • Microsoft SharePoint Administration Toolkit v3.0 x86
    https://www.microsoft.com/en-us/download/details.aspx?id=1219
    http://www.microsoft.com/downloads/details.aspx?familyid=412A9EF1-3358-4420-B820-0CA3F4641651
    • Microsoft SharePoint Administration Toolkit v3.0 x64
    http://www.microsoft.com/en-us/download/details.aspx?id=6368
    http://www.microsoft.com/downloads/details.aspx?familyid=BE58D769-2516-43CB-9890-3F79304528FF

     


    Please remember to click 'Mark as Answer' on the post that helps you or 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,
    Nishant Shah
    Microsoft Online Community Support

    Monday, November 12, 2012 11:27 AM
    Moderator
  • Thanks Nishant,

    It appears that the Batch Site Manager is only recommended for Site Collections up to 15 GB. What do I do about larger Site Collections? (ex. 50 GB)

    Thanks,

    Kelly


    Personal Blog: http://thebitsthatbyte.com

    Monday, November 12, 2012 3:22 PM
  • Hello,

    Both MergeContentDBs and Batch Site Manager uses operation similar to stsadm backup and stsadm restore and hence the recommendation on those sizes on both operations...

    Below TechNet articles outlines

    1. Back up a farm by using SQL Server tools (Office SharePoint Server 2007) - http://technet.microsoft.com/en-us/library/cc263069(v=office.12).aspx
    2. Back up and restore a site by using DPM (Office SharePoint Server) - http://technet.microsoft.com/en-us/library/cc770247(v=office.12).aspx

    Please remember to click 'Mark as Answer' on the post that helps you or 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,
    Nishant Shah
    Microsoft Online Community Support

    Tuesday, November 13, 2012 10:22 AM
    Moderator
  • Thanks. Since I can't move a Site Collection that is 7 GB, I will chalk it up as directly tied to server performance. Is there a timeout switch with the stsadmn I could use so it processes the file?

    Personal Blog: http://thebitsthatbyte.com

    Tuesday, November 13, 2012 3:47 PM
  • Hello,

    Yes, this could potentially be a resource (CPU / Memory / Disk / Network) bottleneck at SharePoint, IIS, SQL or Network levels or combinition of these. You'll need to isolate the issue based on the error(s) before you tweak the various timeout settings.
    You could collect ULS logs (on SP Servers) and PerfMon data (SharePoint / SQL) and then you could start the MergeContentDBs and once it fails, look into the ULS logs / Event Logs / PerfMon data to identify potential issues.

    If you need in-depth level of support (which is not feasible thru Forums), please visit the below link to see the various paid support options that are available to better meet your needs: http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone. If you are a MSDN / TechNet subscriber, you can also contact our support by using your free support incidents.


    Please remember to click 'Mark as Answer' on the post that helps you or 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,
    Nishant Shah
    Microsoft Online Community Support


    Wednesday, November 14, 2012 8:11 AM
    Moderator