none
SharePoint Farm Backup and Restore RRS feed

  • Question

  • Hi All,

    We have a server farm with 2 WFEs,1 App Server, a cluster SQL Server.  We wanted to take scheduled backup of this SharePoint Farm. So what all things need to be backup for successful restore later if required?

    I assume just stsadm backup will be enough, but I wanted to confirm this. Also somebody can point me some good links related to SharePoint back planning.

    Thanks in advance,
    San
    Sunday, April 5, 2009 6:21 PM

Answers

  • John Ferringer's book on DR is very good.  http://www.amazon.com/SharePoint-2007-Disaster-Recovery-Guide/dp/1584505990/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1238981147&sr=8-1

    It all depends on what situation you are trying to restore from.  Are you expecting to come back to the same servers, or possibly to different hardware?  Are you looking to recover from just data loss, or a catastrophic hardware failure?

    The stsadm backup/restore will get you system settings and content.  Any customization to the 12 hive (images, templates, etc) will need to be backed up as well.  I typically have those directories backed up during normal server backups.  Some components may also need to re-installed and configured depending on how they were applied.

    For farms that I have managed I typically try and keep a list of what was installed (web parts, solutions, etc) and I have redundant backup methods just in case.  I try and relay on the SharePoint backups as the primary method, but keep the file and SQL Server backups just in case.

    SharePoint Developer | Administrator | Evangelist -- Twitter -- Blog - http://nextconnect.blogspot.com
    Monday, April 6, 2009 1:32 AM
  • I'm sure I'm a storage vendor's dream customer.  I like big sites, and I love redundant backups.  I know that I don't want to be caught without a usable backup.  I've seen it happen to other servers and its not a pretty sight.

    The SQL backup is redundant to the stsadm backup.  With that said though, if your failure is on the db server and you just need to bring the dbs back the amount of time it takes to restore a db is a very small fraction of what it takes to pump all of the content through the stsadm tool.  It also gives you a fall back if there is a problem with the stsadm backup. 

    SharePoint Developer | Administrator | Evangelist -- Twitter -- Blog - http://nextconnect.blogspot.com
    Monday, April 6, 2009 11:52 PM

All replies

  • John Ferringer's book on DR is very good.  http://www.amazon.com/SharePoint-2007-Disaster-Recovery-Guide/dp/1584505990/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1238981147&sr=8-1

    It all depends on what situation you are trying to restore from.  Are you expecting to come back to the same servers, or possibly to different hardware?  Are you looking to recover from just data loss, or a catastrophic hardware failure?

    The stsadm backup/restore will get you system settings and content.  Any customization to the 12 hive (images, templates, etc) will need to be backed up as well.  I typically have those directories backed up during normal server backups.  Some components may also need to re-installed and configured depending on how they were applied.

    For farms that I have managed I typically try and keep a list of what was installed (web parts, solutions, etc) and I have redundant backup methods just in case.  I try and relay on the SharePoint backups as the primary method, but keep the file and SQL Server backups just in case.

    SharePoint Developer | Administrator | Evangelist -- Twitter -- Blog - http://nextconnect.blogspot.com
    Monday, April 6, 2009 1:32 AM


  • Thanks Mike ..my requirement is, in case something goes wrong with production server website, I should be able to restore the same site either in the same server farm or in another server farm without any data loss.

    So what I understood from you is, if I do stsadm backup and 12 hive folders then i should be fine.....SQL backup looks to me as redundant data as  stsadm backup already takes care of that.. am I right?

    Thanks again,
    San

    Monday, April 6, 2009 5:19 PM
  • I'm sure I'm a storage vendor's dream customer.  I like big sites, and I love redundant backups.  I know that I don't want to be caught without a usable backup.  I've seen it happen to other servers and its not a pretty sight.

    The SQL backup is redundant to the stsadm backup.  With that said though, if your failure is on the db server and you just need to bring the dbs back the amount of time it takes to restore a db is a very small fraction of what it takes to pump all of the content through the stsadm tool.  It also gives you a fall back if there is a problem with the stsadm backup. 

    SharePoint Developer | Administrator | Evangelist -- Twitter -- Blog - http://nextconnect.blogspot.com
    Monday, April 6, 2009 11:52 PM
  • Thanks Mike ..Thanks for your input
    Tuesday, April 7, 2009 6:29 AM