Recovering after a failed upgrade (SharePoint Foundation 2010)
Applies to: SharePoint Foundation 2010
Topic Last Modified: 2011-09-15
If the upgrade to Microsoft SharePoint Foundation 2010 has failed and you do not have time to continue to troubleshoot the issues or resume the upgrade process, you have to recover your Windows SharePoint Services 3.0 environment. The steps differ depending on the type of backup you have. If you were performing a database attach upgrade and you kept your original environment available — either by using read-only databases or by taking the environment offline — you can recover your environment easily. If you were performing an in-place upgrade, you must recover your entire environment and restore the data.
If you do have time, you should troubleshoot the issues and resume upgrade. For more information, see Troubleshoot upgrade issues (SharePoint Foundation 2010) and Resume upgrade (SharePoint Foundation 2010).
In this article:
When you perform a database attach upgrade, you can choose to leave your existing environment available, but with the databases set to read-only. Recovering when you are in this state is the simplest recovery path, because your original environment is still available, it is merely set to read-only. If you have to recover your environment, you can merely switch the databases to read/write again and resume serving requests. The article Run a farm that uses read-only databases (Windows SharePoint Services) describes the steps you take to set a farm to use read-only databases. To return the read-only farm to full operations, you set the Database Read-Only entry back to False, and then re-enable the timer jobs listed in the article.
If you created a full backup of your environment before you started the upgrade process, you can restore that full backup to recover your environment. For more information about how to restore from a full backup, see Restore a farm by using built-in tools (Windows SharePoint Services 3.0).
If you only created backups of your content databases, you can still recover your environment, but it will take longer and involve more steps. You basically have to build out your environment again and then restore the database backups. For more information about how to recover an environment and restore backed up content databases, see Restore a farm after a configuration database problem (Windows SharePoint Services).