SharePoint 2010 Backup Strategy

Posted on 2012-09-12
Last Modified: 2012-09-20
I need some help with creating a backup strategy for SharePoint 2010, backend using SQL 2008 R2.  Can someone please give some insight, or point me in the right direction to a good site to read about it.

I've read a number of things, but it's all kind of confusing.  What technology should be used, PowerShell or SQL backups?  

I've read that Sharepoint should be used for the config and central administration content database backups...but then SQL backups can be used for all the other databases.  SharePoint should be the only option for the config/administration content database, because if you try to restore a SQL backup of these databases you'll corrupt the database.  Can someone cofirm and/or deny, with some explanation?

If SharePoint should be used for those two databases, then why not simply use SharePoint for all databases?  I'm assuming that SQL backups would be more efficient, but what else would I be gaining from using SQL backups?  Is it just point-in-time recovery, with the transaction logs?

It seems as though I'd be creating a headache for myself if I were to backup some of the databases using SharePoint and SQL backups for other databases.

Point is, I need to create a strategy and I'd like to know what I'm talking about before making any recommendations.

Question by:CoreyAnt
    LVL 3

    Accepted Solution


    regarding the SQL database behind Sharepoint, it'd be better to take SQL backup.

    Create a Maintenance Plan for each of the following:

    - Full Database backup (must include all the "use database", with a backup file for every DB)
    - Incremental backup (differential, with the same options as the FULL)
    - Transaction logs backup (only for the Sharepoint DB's )

    In this way you are sure you can restore any version of the DB as per your policy and just restart the Sharepoint software immediately after.

    I was discouraged by Sharepoint guru to make it differently, since the backup will be less reliable and more difficult to restore. The SQL backup can be easily moved to a new machine and then used to rebuild all the configuration.

    I don't understand why a backup made by SQL should corrupt the DB itself if restored. It's the native way to do it, and it works pretty well. Of course, you need to have the transaction logs backup, otherwise you risk to compromise the integrity of the DB and Sharepoint might present several issues.

    Hope it helps.

    Author Comment

    Alright, I appreciate your suggestions.  I've just read in a couple of locations that restoring the configuration database and the central administration database from a SQL backup is not supported, some even saying that it simply won't work and you may corrupt the database.  But in theory, I completely agree with you...I'm just concerned because of the difference in opinion out there.

    I wonder if anyone else can confirm what I'm thinking and what you're saying.
    LVL 3

    Expert Comment

    Well, I must say that on the first configuration I had the opportunity to talk with an high expert and he confirmed this was the best option for the Sharepoint backup. Indeed it's the one I use. It'd be nice to hear from other experts btw.

    Kind regards

    Featured Post

    Better Security Awareness With Threat Intelligence

    See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

    Join & Write a Comment

    SharePoint Designer 2010 has tools and commands to do everything that can be done with web parts in the browser, and then some – except uploading a web part straight into a page that is edited in SPD. So, can it be done? Scenario For a recent pr…
    I thought I'd write this up for anyone who has a request to create an anonymous whistle-blower-type submission form created using SharePoint 2010 (this would probably work the same for 2013). It's not 100% fool-proof but it's as close as you can get…
    Via a live example, show how to setup several different housekeeping processes for a SQL Server.
    Viewers will learn how to use the SELECT statement in SQL and will be exposed to the many uses the SELECT statement has.

    746 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    17 Experts available now in Live!

    Get 1:1 Help Now