How the upgrade process works (Office SharePoint Server)
Applies To: Office SharePoint Server 2007
This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.
Topic Last Modified: 2016-11-14
In this article:
How URL redirects are handled during gradual upgrade
How shared services change the gradual upgrade process
You can choose among three upgrade approaches: in-place, gradual, and database migration. An in-place upgrade is used to upgrade all Microsoft® SharePoint® sites at one time, which is best suited for single server or small deployments. A gradual upgrade allows finer control of the upgrade process by allowing one or more site collections to be upgraded at a time. Both in-place and gradual upgrades take place on the same hardware on which your previous version is installed. A database migration allows you to move your content to a new farm or new hardware.
For larger deployments, a gradual upgrade is a better option than an in-place upgrade because it enables the administrator performing the upgrade to control how many site collections to upgrade at one time. In this way, large deployments can be upgraded gradually over several weekends while continuing to host the previous version sites. This is possible because you can continue to host the sites that have not yet been upgraded on the same server as the upgraded sites.
In an in-place upgrade:
The previous version is overwritten with the new version, and the content databases are changed. Because of this, an in-place upgrade is not a reversible process — that is, you cannot roll back to the previous version.
The original sites are upgraded in place, and you cannot view the previous versions of the sites after upgrade.
All sites are unavailable to site visitors during upgrade. The period during which the sites are unavailable is the full time it takes to upgrade the entire server or server farm.
Site visitors continue to use the same URLs after upgrade.
In a gradual upgrade:
As each group of site collections is upgraded, the upgrade process copies the data in them from the original database to a new database before upgrading the data. The original data is maintained in the original database until explicitly deleted by the server administrator. Because of this, upgraded sites can be easily rolled back to the previous version if necessary.
Most sites are available to site visitors during the upgrade; only those site collections that are currently being upgraded are offline. (Note that the previous version sites are marked as updates only after they have been copied in preparation for upgrade.)
The upgrade impact is limited to only those users who need the site or sites being upgraded.
After upgrade, the original URLs point to the upgraded version of the sites. This way, users can continue to use the same URLs they used before the upgrade.
A database migration is essentially an in-place upgrade that you perform on a copy of the content. In a database migration:
You copy all databases except for the configuration and search databases, and then add the databases to a new stand-alone or server farm installation.
When you attach the databases to the new server farm, the upgrade process runs and upgrades the data in place.
Because of the downtime, and the risk that upgrade may take longer than expected or that some sites may need some rework after upgrade, it is critical that the server administrator communicate with site owners and users about what to expect during the process. For more information, see Create communication plan.
An in-place upgrade takes place on the same hardware as your previous version installation. When you run an in-place upgrade, the process upgrades your entire installation in a pre-set sequence. The following steps explain what happens as the in-place upgrade process runs:
After performing all pre-upgrade steps, the server administrator installs Microsoft Office SharePoint Server 2007 to the server running Microsoft Office SharePoint Portal Server 2003 and chooses In-place Upgrade.
The upgrade process runs and upgrades the configuration database and the Central Administration site.
The upgrade process runs and upgrades any data specific to the server (for example, search settings).
The upgrade process runs on each virtual server and upgrades each site collection in that virtual server.
After all sites have been upgraded, the upgrade process ends.
Repeat the upgrade action on each server in a server farm environment.
The administrator confirms that upgrade is complete and then uninstalls SharePoint Portal Server 2003.
Similar to an in-place upgrade, a gradual upgrade takes place on the same hardware that is used for your previous version installation. However, a gradual upgrade allows you to control when upgrade takes place for each individual site collection, and it also allows you to continue running the previous version and the new version side by side on that hardware. When you perform a gradual upgrade, the starting and ending topologies have the same configuration, similar to an in-place upgrade except for the following differences:
During and after upgrade, the front-end Web servers run both SharePoint Portal Server 2003 and Office SharePoint Server 2007. Any upgraded site collections run under Office SharePoint Server 2007, whereas site collections that could not be upgraded or that were not selected for upgrade continue to run under SharePoint Portal Server 2003.
Scenarios in which you may not want to upgrade sites include: you may need to keep some sites in the previous version until a needed language pack is available for the current version, or you may need to wait for a new custom site definition to be created.
During and after upgrade, the application servers run both SharePoint Portal Server 2003 and Office SharePoint Server 2007 services. Upgraded portal sites consume Office SharePoint Server 2007 shared services; portals that have not yet been or cannot be upgraded consume SharePoint Portal Server 2003 shared services. Additional services (such as Microsoft Excel® services) can be added after upgrade.
During and after upgrade, both the SharePoint Portal Server 2003 and the Office SharePoint Server 2007 databases are available. Content for upgraded sites is stored in the Office SharePoint Server 2007 databases; content for sites that could not be upgraded or that need to remain as they were continue to be stored in the SharePoint Portal Server 2003 databases. Configuration databases exist for both Office SharePoint Server 2007 and SharePoint Portal Server 2003.
The following figure illustrates the gradual upgrade process:
The following steps correspond to the callout numbers in the preceding figure and explain what happens as the gradual upgrade process runs.
After performing all pre-upgrade steps, the server administrator installs Office SharePoint Server 2007 to the first front-end Web server in the farm and then chooses Gradual Upgrade.
It is recommended that you back up your environment before running the upgrade. For more information, see Run and test a full backup in SQL Server.
The upgrade process runs and upgrades any data specific to each server (for example, search settings stored on the file system on SharePoint Portal Server 2003 servers).
The upgrade process creates a Office SharePoint Server 2007 Web application to host SharePoint Central Administration, and the Central Administration site is created.
The upgrade process creates a new configuration database to store configuration data for Office SharePoint Server 2007. Configuration data from the SharePoint Portal Server 2003 configuration database is copied into the new database.
After Office SharePoint Server 2007 has been installed to the first front-end Web server, the administrator installs it to all other servers in the server farm. If the environment uses shared services, the upgrade process upgrades user profiles and search data (this data is specific to the portal site that was selected).
The administrator selects a virtual server to upgrade and specifies the target Web application. The upgrade process creates the target Web application and adds any Web Parts deployed to the SharePoint Portal Server 2003 virtual server to the new Web application.
The upgrade process creates a temporary content database for each content database that exists in the previous version. The upgrade process copies the site list from SharePoint Portal Server 2003 into the new environment. The administrator selects the site collections to upgrade. The upgrade process copies the data for those sites into the temporary content database, and then upgrades those sites in that temporary content database. Each site is temporarily unavailable while being copied into the temporary content database.
After the content has been upgraded, the upgrade process moves the data to the Office SharePoint Server 2007 content database and then deletes the temporary content database.
At the end of the upgrade process, SharePoint Portal Server 2003 and Office SharePoint Server 2007 are both running and available. After all sites have been upgraded, the administrator confirms that upgrade is complete. If SharePoint Portal Server 2003 is no longer needed, the administrator uninstalls SharePoint Portal Server 2003.
How URL redirects are handled during gradual upgrade
Two sites cannot share the same URL. Therefore, during a gradual upgrade, when you have both the old version and the new version of each site, you need two different domain URLs for each site (for example, http://*company\_name*/sites/Site and http://*company\_name*\_V2/sites/Sit). During upgrade, a temporary domain URL is needed to host the original previous version sites. The new version takes over the domain URL that points to the content prior to upgrade, and user requests will be routed to their content whether or not it has been upgraded. The following process occurs during upgrade to make this redirection possible:
Before you begin the upgrade, create a temporary URL domain for your previous version sites.
When you run the upgrade, the upgrade process will ask you for the domain you specified above. The process moves the previous version site to the temporary URL domain, and the new version site takes over the original URL domain.
A redirect is created automatically for each site collection to send requests for the original URL to the previous version site until the site is upgraded.
After each site has been upgraded, the redirect for that site is dropped.
After all sites have been upgraded, and after you have deleted all of the previous version sites and completed the upgrade process, you can manually remove the temporary URL domain from the Domain Name System (DNS).
During this process, browse access to the original URL always works. However, certain client applications (such as Microsoft Office client applications) cannot use these types of redirects. For more information, see Comparison of key features. Before a site is upgraded, the original URL points to the previous version; after a site has been upgraded, the original URL points to the new version.
The following table illustrates how the URLs work during gradual upgrade.
|Stage||Original site URL||Upgraded site URL||Notes|
The server administrator creates http://company_name_V2 for use during gradual upgrade.
Requests for http://company_name/sites/SiteA are redirected to http://company_name_V2/sites/SiteA until it is upgraded.
http://company_name_V2/sites/SiteA (until deleted)
The redirect is removed after upgrade is complete and the results are validated.
Be aware that this URL redirection can cause hard-coded links within sites or documents to break. For example, Microsoft Office InfoPath® forms sometimes contain hard-coded links to a data location (such as a specific SharePoint list, Web service, or XML file). Because the link is hard-coded, it cannot be automatically updated to point to the temporary URL used for sites that have not yet been upgraded during a gradual upgrade. Use a trial upgrade to identify such issues before you begin your official upgrade process. That way, you can identify any sites that need to be upgraded quickly so that they can use the original URL again, and you can avoid the support calls that result from loss of functionality in forms or other items containing hard-coded links.
How shared services change the gradual upgrade process
If you use shared services in SharePoint Portal Server 2003, the gradual upgrade process is more complicated. It follows the same rough outline, but you must repeat the steps for the parent portal site and all child portal sites.
During a gradual upgrade with shared services:
The SharePoint Portal Server 2003 parent portal site continues to provide services to sites that are configured to consume shared services.
The SharePoint Portal Server 2003 sites that consume shared services retain the same user experience.
Two search crawls are performed: by default, Office SharePoint Server 2007 crawls everything that was crawled by SharePoint Portal Server 2003, and the SharePoint Portal Server 2003 search service continues to crawl the SharePoint Portal Server 2003 environment. (Note that Office SharePoint Server 2007 can crawl the SharePoint Portal Server 2003 sites, but SharePoint Portal Server 2003 cannot crawl the Office SharePoint Server 2007 sites.) This means that you may be using up to twice the amount of network bandwidth for search crawling during a gradual upgrade with shared services. To minimize the impact, you can reduce the scope of either the previous version or the Office SharePoint Server 2007 crawls and, as SharePoint Portal Server 2003 sites are upgraded, you can delete their start addresses from the SharePoint Portal Server 2003 search settings.
User profile and audience data is modified in one location — Office SharePoint Server 2007 — and is pushed from Office SharePoint Server 2007 to the SharePoint Portal Server 2003 environment by way of a scheduled job run by the SharePoint timer service.
When you upgrade with shared services, upgrade the parent portal site first, and then any child portal sites. However, if you need to upgrade a child portal site first (for example, if you only want to upgrade a single child portal site, and not any other child portal sites or the parent portal site), you can instead:
Create a temporary Shared Services Provider (SSP) in a new Office SharePoint Server 2007 environment.
Upgrade the child portal site and point it to the temporary SSP for services.
Download this book
This topic is included in the following downloadable book for easier reading and printing:
See the full list of available books at Downloadable content for Office SharePoint Server 2007.