SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are planning to update our MOSS 2007 Enterprise SP2 environment to SP3. I wanted to know a rollback strategy that we should plan just in case our update fails. Although we will doing this update in test environment first, but still. Can we just take the DB backups of all content, my sites and central admin DBs and restore them just in case we face any issues?

share|improve this question
up vote 1 down vote accepted

Backups are probably your best option, given that there isn't a way to uninstall a SharePoint patch, but you should keep a few things in mind:

  • Make sure you know what version your farm is on when you take the backups, and that you have the files available to rebuild a replacement farm to exactly that patch level. You may be able to restore older backups into a newer farm but that's getting more and more difficult as the products evolve.
  • Keep in mind that you'll need to do a full rebuild of the farm and then restore those content databases to the new farm, so it is important to capture how you have the farm configured so you can build a new farm to match the old one.
  • The content databases are the main thing you'll want to target for backups. If you're doing SQL Server database backups, Microsoft does not support restoring configuration databases from SQL Server backups.


share|improve this answer
So if I understand correctly for your last point, rather than taking a SQL DB backup for your SP farm, you probably should take the stsadm/CA backup way for backing up your farm databases. – Ashish Aug 27 '12 at 12:51

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.