Export (0) Print
Expand All

Roadmap: in-place upgrade with detached databases (SharePoint Server 2010)

SharePoint 2010

Published: May 12, 2010

When you upgrade from Microsoft Office SharePoint Server 2007 to Microsoft SharePoint Server 2010, you can perform an in-place upgrade or a database attach upgrade, or you can combine certain aspects of both approaches to increase availability or throughput during the upgrade process. This article describes how to perform a hybrid approach that combines in-place upgrade with detaching and attaching databases so that you can upgrade multiple databases at the same time, possibly even on separate hardware. You can use this approach to upgrade two or more content databases at a time, and therefore upgrade more quickly than if you used a standard in-place upgrade (which upgrades individual content databases and site collections serially). This approach uses the following hybrid techniques:

  • Use an in-place upgrade to upgrade the farm and settings.

  • Detach and upgrade multiple databases in parallel.

  • Alternative upgrade sequence: Upgrade databases on a temporary small farm.

Note that if you decide to use a temporary small farm to perform the actual upgrade, you must have direct access to the database servers to copy the databases from. Copying databases over the network takes time and bandwidth — make sure you test this process to determine whether you have the resources you need to use a temporary small farm.

For more information about the pros and cons of the different upgrade approaches, see Determine upgrade approach (SharePoint Server 2010). For a brief overview and graphical description of the steps you take for each approach, see Upgrade process overview (SharePoint Server 2010).

note Note:

One frequent cause of failures during upgrade is that the environment is missing customized features, solutions, or other elements. Be sure that any custom elements you need are installed on your front-end Web servers before you begin the upgrade process. You can use the pre-upgrade checker — and, for a database attach upgrade, the test-spcontentdatabase Windows PowerShell cmdlet — to identify any custom elements that your sites might be using. For more information, see Identify and install customizations in the article "Use a trial upgrade to find potential issues."

In this article:

Important Important:

You must be running Service Pack 2 (SP2) of Office SharePoint Server 2007 in a 64-bit Windows Server 2008 environment to perform an in-place upgrade to SharePoint Server 2010. If you are in a server farm environment, you must also be running a 64-bit version of one of the following: Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, and SQL Server 2005 with SP3 and Cumulative Update 3.

Process overview

Because this upgrade approach is a hybrid of the techniques used for in-place upgrade and database attach upgrade, this article describes how the steps from each approach fit together into the hybrid process. It does not provide details for every step in the process, because those steps are available in the following articles:

These articles, combined with this roadmap, give you the information you need to perform this hybrid upgrade.

There are two ways in which you can perform this type of hybrid upgrade: using one farm throughout or using a temporary small farm to perform the actual upgrade. The sections below provide the steps you need to take to perform the upgrade by using each of these methods.

Before you begin

Before you begin the in-place upgrade, review the following information about permissions, hardware requirements, and software requirements and steps to perform before beginning the process.

To detach databases and upgrade them in parallel on the same farm

This section describes the steps to take to use the detach databases upgrade approach on a single farm.

Process for upgrading in-place with detached databases (same farm)

Detach databases

  1. Use the following operation to detach the content databases:

    Stsadm.exe -o deletecontentdb -url http://servername -databasename ContentDatabaseName

    For more information about this operation, see Deletecontentdb: Stsadm operation (Office SharePoint Server).

Upgrade the farm in place

  1. Install all prerequisites to all servers in the farm.

  2. Run Setup on all servers in the farm.

  3. Run the SharePoint Products Configuration Wizard on all servers in the farm.

For detailed procedures that describe these steps, see Upgrade in place to SharePoint Server 2010.

Attach the databases and upgrade the content

  1. Add the content databases to the Web applications.

    Use the following Windows PowerShell cmdlet to add and upgrade the content databases:

    Mount-SPContentDatabase -Name <DatabaseName> -DatabaseServer <ServerName> -WebApplication <URL> [-Updateuserexperience]
    
  2. Verify upgrade for the first database.

  3. Repeat the restore-and-add-database procedures for remaining databases in parallel.

For detailed procedures that describe these steps, see Perform a database attach upgrade to SharePoint Server 2010.

To detach databases and upgrade them in parallel on a temporary small farm

This section describes the steps to take to use the detach databases upgrade approach on two farms: the original farm and a temporary small farm.

Process for upgrading in-place with detached databases (temporary small farm)

Set up a temporary small farm to use in upgrading the databases

For detailed procedures that describe these steps, see Prepare the new SharePoint Server 2010 environment for a database attach upgrade.

2 - Detach databases from the original farm

  1. Back up the previous version databases by using SQL Server tools.

    For detailed procedures about backing up the databases, see Perform a database attach upgrade to SharePoint Server 2010.

  2. Use the following operation to detach the content databases:

    Stsadm.exe -o deletecontentdb -url http://servername -databasename ContentDatabaseName

    For more information about this operation, see Deletecontentdb: Stsadm operation (Office SharePoint Server).

Upgrade the original farm in place

  1. Install all prerequisites to all servers in the farm.

  2. Run Setup on all servers in the farm.

  3. Run the SharePoint Products Configuration Wizard on all servers in the farm.

For detailed procedures that describe these steps, see Perform an in-place upgrade (SharePoint Server 2010).

Attach the databases to the temporary small farm and upgrade the content

  1. Restore the backup copy to the new farm.

  2. Add the content databases to the Web applications.

    Use the following Windows PowerShell cmdlet to add and upgrade the content databases:

    Mount-SPContentDatabase -Name <DatabaseName> -DatabaseServer <ServerName> -WebApplication <URL> [-Updateuserexperience]
    
  3. Verify upgrade for the first database.

  4. Repeat the restore-and-add-database procedures for remaining databases in parallel.

For detailed procedures that describe these steps, see Perform a database attach upgrade to SharePoint Server 2010.

Back up the databases from the temporary small farm and attach them to the original farm

  1. Back up the upgraded databases by using SQL Server tools.

  2. Restore the backup copy to the original farm.

  3. Add the upgraded content databases to the original Web applications.

This is basically the same process as the previous step; however, you are moving the databases from the temporary small farm back to the original farm. The same procedures apply as in the previous steps.

Verification

If upgrade fails or reports issues, you can refer to the log and error files for more information. For more information about reviewing the log files, and about restarting upgrade after a failure, see Verify upgrade and review upgraded sites (SharePoint Server 2010).

Additional steps

After you have completed the upgrade, there are several steps that you should take to complete the configuration for your new farm. For more information, see Perform post-upgrade steps for an in-place upgrade (SharePoint Server 2010).

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft