locked
Site Collection Backup suggestions? RRS feed

  • Question

  • Hi,

    We have scheduled site collection backup in our farm on a daily basis. It was running fine. But in recent days due to increase in the number of site collections & the size of the sites, it takes more than 15 hours to complete the backup process which affects the users.

    Any best practices can be suggested...


    Thanks,
    Chanakya
    Microsoft Certified Professional
    My Blog
    • Edited by Mike Walsh FIN Wednesday, August 3, 2011 7:31 AM The word required was removed from the title and replace by a ? Required is far too pushy.
    Wednesday, August 3, 2011 7:29 AM

Answers

  • Hi Chanakya, you can do it step by step or use Stsadm command Backup/restore

    http://technet.microsoft.com/en-us/library/cc263441%28office.12%29.aspx

    If you use the Stsadm Backup/Restore you are not backing up Database But the Site Collection data.

    You can create a new Site Collection with a Database and migrate using the stsadm  backup and restore

    First you define which Site collection you want to migrate to new Database, then send a notification to your customers and block the site to read-only using "stsadm -o setsitelock"

    http://technet.microsoft.com/en-us/library/cc262811%28office.12%29.aspx

    There you user can access content but cannot change, after you migrate and everything looks fine, you block access to older Site Collection or create a page or add html to redirect  for new Site collection "<meta http-equiv="refresh" content="0;url=http://MYSERVERNAME.com/Pages/default.aspx">"

    Then you are changing the architecture and you can manage multiple site collections with different databases.

     


    André Lage Microsoft SharePoint, CRM and Sybase Consultant
    Blog:http://aaclage.blogspot.com
    Codeplex:http://spupload.codeplex.com/http://simplecamlsearch.codeplex.com/
    • Marked as answer by Emir Liu Friday, August 12, 2011 10:18 AM
    Wednesday, August 3, 2011 11:46 AM
  • Here is what I suggest

    • Identify if any of the site collections sharing the same content DB is large or not. This you can do using stsadm enumsites
    • Using stsadm mergecontentDB command move it to a new content DB. Refere link http://technet.microsoft.com/en-us/library/cc825327(office.12).aspx
    • The you can schedule SQL full, incremental backup as per your need
    • For site collections that share content DB, you can also schedule SQL backup but when you have to restore, it is better that you restore it in a different farm, and then using stsadm backup and restore method copy it into live farm. This suggestion to copy it into a different farm is to avoid overwriting of data on other sites which are also sharing the same content DB.

     


    Thanks & Regards,

    Soumyadev | Posting is provided "AS IS" with no warranties, and confers no rights.

    • Proposed as answer by M Hussain Thursday, August 4, 2011 10:38 AM
    • Marked as answer by Emir Liu Friday, August 12, 2011 10:18 AM
    Wednesday, August 3, 2011 11:14 PM

All replies

  • Hi Chanakya,

     

    As I understand, you schedule a site collection backup from SharePoint. I would rather sugggest you to schedule a Full backup on a weekly basis and Diff. backup on a daily basis from SQL Server for all the content DBs with logs including farm config database. You have to ensure the databases  mode should be Full Recovery.

    By this way of scheduling a backup will reduce much more time compare to SP and its comparatively safe.  


    Mohammed Hussain
    Wednesday, August 3, 2011 10:18 AM
  • Hi Mohammed,

     

    Thanks for your reply.

    In such case of a DB backup, What if I need to restore a single site collection from the backup??

    Will it be possible? If yes, then how to go with that??


    Thanks,
    Chanakya
    Microsoft Certified Professional
    My Blog
    Wednesday, August 3, 2011 10:21 AM
  • Hi Chanakya Jayabalan,

    You can create site collection with different databases, this will give some flexibility on your backups and manage times for backups.

    Can use STSADM Commnad to manage your Site Collection Databases.

    http://technet.microsoft.com/en-us/library/cc262407%28office.12%29.aspx

    Can also recomend manage your database and follow some best  practices.

    http://office.microsoft.com/download/afile.aspx?AssetID=am102632301033


    André Lage Microsoft SharePoint, CRM and Sybase Consultant
    Blog:http://aaclage.blogspot.com
    Codeplex:http://spupload.codeplex.com/http://simplecamlsearch.codeplex.com/
    Wednesday, August 3, 2011 11:29 AM
  • Hi Andre,

    The issue I am facing is for the current setup where there are about 120 site collections contained in only 2 content DB's.

    Is there any way available to restore a particular site collection from a DB backup??


    Thanks,
    Chanakya
    Microsoft Certified Professional
    My Blog
    Wednesday, August 3, 2011 11:34 AM
  • Hi,

    If you have any different environment like dev or staging you can take the backup of the content database over there and restore it. Then you can take the STSADM backup of your site collection and can restore it back in your production environment.

    In this way you can carry out the backups as the database level and thsi will improve your maintainance plans.

    Thanks,

    Rahul Rashu


    • Edited by Rashu,Rahul Wednesday, August 3, 2011 11:40 AM typo
    Wednesday, August 3, 2011 11:40 AM
  • Hi Chanakya, you can do it step by step or use Stsadm command Backup/restore

    http://technet.microsoft.com/en-us/library/cc263441%28office.12%29.aspx

    If you use the Stsadm Backup/Restore you are not backing up Database But the Site Collection data.

    You can create a new Site Collection with a Database and migrate using the stsadm  backup and restore

    First you define which Site collection you want to migrate to new Database, then send a notification to your customers and block the site to read-only using "stsadm -o setsitelock"

    http://technet.microsoft.com/en-us/library/cc262811%28office.12%29.aspx

    There you user can access content but cannot change, after you migrate and everything looks fine, you block access to older Site Collection or create a page or add html to redirect  for new Site collection "<meta http-equiv="refresh" content="0;url=http://MYSERVERNAME.com/Pages/default.aspx">"

    Then you are changing the architecture and you can manage multiple site collections with different databases.

     


    André Lage Microsoft SharePoint, CRM and Sybase Consultant
    Blog:http://aaclage.blogspot.com
    Codeplex:http://spupload.codeplex.com/http://simplecamlsearch.codeplex.com/
    • Marked as answer by Emir Liu Friday, August 12, 2011 10:18 AM
    Wednesday, August 3, 2011 11:46 AM
  • Here is what I suggest

    • Identify if any of the site collections sharing the same content DB is large or not. This you can do using stsadm enumsites
    • Using stsadm mergecontentDB command move it to a new content DB. Refere link http://technet.microsoft.com/en-us/library/cc825327(office.12).aspx
    • The you can schedule SQL full, incremental backup as per your need
    • For site collections that share content DB, you can also schedule SQL backup but when you have to restore, it is better that you restore it in a different farm, and then using stsadm backup and restore method copy it into live farm. This suggestion to copy it into a different farm is to avoid overwriting of data on other sites which are also sharing the same content DB.

     


    Thanks & Regards,

    Soumyadev | Posting is provided "AS IS" with no warranties, and confers no rights.

    • Proposed as answer by M Hussain Thursday, August 4, 2011 10:38 AM
    • Marked as answer by Emir Liu Friday, August 12, 2011 10:18 AM
    Wednesday, August 3, 2011 11:14 PM