Upgrade approaches share_pointproducts
0 likes210 views
This document discusses different approaches for upgrading from Microsoft Office SharePoint Server 2007 or Windows SharePoint Services 3.0 to Microsoft SharePoint 2010 Products. It describes an in-place upgrade approach where the new version of SharePoint 2010 Products is installed on the same hardware as the previous version, upgrading the content and settings during a single process. The advantages are that farm-wide settings are preserved and upgraded and customizations remain available after upgrade, though manual steps may be needed. The disadvantages are servers and farms are offline during the upgrade and it proceeds continuously without pausing.
Upgrade approaches share_pointproducts
- 1. Microsoft SharePoint 2010 Products Upgrade Approaches Basic upgrade approach “building blocks” For more information about planning for upgrade, see the Upgrade Planning model. When you are planning an upgrade from Microsoft® Office SharePoint® Server 2007 Note that the diagrams on this page use the same topology for simplicity. Your In addition, this standard topology is based on Office SharePoint Server 2007. or Windows SharePoint Services 3.0 to Microsoft SharePoint 2010 Products, think of beginning and ending topologies will depend on your current topologies and on the Windows SharePoint Services 3.0 topologies are similar, but do not contain the the different upgrade approaches as building blocks that you can use to create your capacity planning work you do for SharePoint 2010 Products. Application server layer or SSP databases. own optimal upgrade approach. The following upgrade approaches are available in SharePoint 2010 Products. Farm before upgrade Topology in transition Upgrade complete In-place upgrade Original Upgrade sequence Original Original Visual Upgrade Description farm User farm User farm User requests requests requests Preview sites in the SharePoint 2010 1 Run Setup on the first front-end Web Products look. Complete the change to the You use in-place upgrade to install the new version of server in the farm. SharePoint 2010 Products look when you SharePoint 2010 Products on the same hardware that Run Setup on the remaining front-end are ready. 2 you used for the previous version. You upgrade the Web servers and application servers. 1 2 content and settings in the server farm as part of a 3 Run the SharePoint Products 3 single process. Configuration Wizard on the front-end 4 Web server that is running the Front-end Web servers SharePoint Central Administration Central Front-end Web servers Front-end Web servers Web site. This server, the Admin Advantages Disadvantages configuration database, the services, and the content databases are · Farm-wide settings are preserved and upgraded. · Servers and farms are offline while the upgrade is in Application upgraded sequentially. 2 Application · servers Application Customizations are available in the environment progress. Run the SharePoint Products servers 4 servers 4 after the upgrade, although manual steps may be · The upgrade proceeds continuously; consequently, Configuration Wizard on the remaining required to upgrade or rework them. you must allow time for all content to be upgraded in servers. turn. 3 Database Database Database Database Database Database Database Database Database server 1 server 2 server 3 server 1 server 2 server 3 server 1 server 2 server 3 (content (services (config (content (services (config (content (services (config DBs) DBs) DB) DBs) DBs) DB) DBs) DBs) DB) Database attach upgrade to a new farm Original farm Original farm Upgrade sequence New farm Original farm New farm http://contoso1 User http://contoso1 User http://contoso2 User http://contoso1 User http://contoso2 User Description requests 2 requests Set up and configure the new farm. 1 requests requests 4 requests 1 Transfer customizations to the new You can use a database attach upgrade to upgrade the farm and test the environment. content for the environment on a separate farm. The result is that you do not upgrade any of the services or 2 Detach the content database from the old farm and take the old farm offline. farm settings. You can upgrade the content databases in any order and upgrade several databases at the same 3 Attach the content databases to the time. You can attach a Shared Services Provider (SSP – Front-end Web servers Front-end Web servers new farm and upgrade the content. Front-end Web servers Front-end Web servers Front-end Web servers Office SharePoint Server 2007 only) database during Start serving requests on the new 4 database attach upgrade, and it will upgrade the profile farm at the new URL. information in the database. You cannot upgrade a Application Application Application Application Application Search database by using this method. servers servers servers servers servers Advantages Disadvantages 3 · You can upgrade multiple content databases at the · The server and farm settings are not upgraded. same time, which results in faster upgrade times You must manually transfer settings that you want Content overall than an in-place upgrade. to preserve from the old farm to the new farm. database · You can use a database attach upgrade to · Any server-side customizations must also be 1-n consolidate multiple farms into one farm. transferred and upgraded manually. Any missing Database Database Database Database Database Database Database Database Database Database Database Database Database Database Database customizations may cause unintended loss of server 1 server 2 server 3 server 1 server 2 server 3 server A server B server C server 1 server 2 server 3 server A server B server C (content (services (config (content (services (config (content (services (config (content (services (config (content (services (config functionality or user experience issues. DBs) DBs) DB) DBs) DBs) DB) SSP DBs) DBs) DB) DBs) DBs) DB) DBs) DBs) DB) · Copying databases across the network takes time database and bandwidth. You must plan for that. · You need direct access to the database servers. Hybrid approaches: combine building blocks Improve upgrade efficiency Minimize downtime during an upgrade A hybrid approach lets you take advantage of in-place The following techniques can be used in a upgrade’s ability to upgrade content and settings, What is downtime? What can I do to mitigate downtime? hybrid approach: while you take advantage of the speed of a database If users cannot connect to their content or data, they are experiencing attach upgrade. · Set databases to read-only while the upgrade is in downtime. Optimize the environment before you upgrade Test, test, test, and test again progress on another farm. · Follow all recommendations in the pre-upgrade · Testing is the only way to estimate how much When you combine in-place and database · Perform database upgrades in parallel: What affects downtime during an upgrade? checker to clean up orphans and address other time is needed for upgrade. attach upgrade techniques: · Upgrade databases in a temporary farm (this can Factors that affect downtime include the following: issues in the environment. · Test by using comparable hardware to gauge · Farmwide settings can be preserved and be a small farm for efficiency), and then reattach to · The upgrade approach you choose · Consider splitting large databases. upgrade speed. upgraded. the original farm. · The size, number, and shape of databases in the environment · Transition to faster hardware before you upgrade · Test by using real data (preferably, you can use · · Upgrade databases in the same farm, but in Customizations are available in the environment after upgrade, although manual steps may be parallel. · How effective and accurate your upgrade testing was (64-bit hardware with Microsoft SQL Server® copies of your current data). 64-bit editions is required). required to upgrade or rework them. · For complex, long-running upgrades, use alternate · Server performance Use Visual Upgrade Choose an upgrade approach that is optimized · You can upgrade multiple content databases at the access mapping to redirect requests. Map sites from · By using Visual Upgrade, site owners can for speed same time, which results in faster upgrade times the new farm to the old farm while the upgrade is in determine when they are ready to switch to the · Database attach or hybrid upgrade overall than an in-place upgrade. progress. new look. Farm before upgrade Topology in transition Upgrade complete Hybrid approach 1: Read-only databases Hybrid techniques used Disadvantages New farm Original farm New farm Original Upgrade sequence 1 User User User · Set databases to read-only while the upgrade is in · The server and farm settings are not upgraded. farm User requests requests requests requests progress on another farm. You must manually transfer settings that you want Set up and configure the new farm. 1 · Perform database upgrades in parallel: to preserve from the old farm to the new farm. Transfer customizations to the new · Upgrade databases in a separate farm · Any customizations must also be transferred and farm and test the environment. · Upgrade multiple databases in parallel upgraded manually. Any missing customizations 2 On the original farm, change content may cause unintended loss of functionality or user databases to read-only. Back up and restore the content databases to the experience issues. Advantages Front-end Web servers new farm. Front-end Web servers Front-end Web servers Front-end Web servers · Copying databases across the network takes time 3 On the new farm, attach the content · The existing farm can continue to host non- and bandwidth. You must plan for that. databases to run the upgrade on the upgraded sites (in read-only mode) while you · You need direct access to the database servers. content. upgrade the content. As a result, users will Application Application Upgrade databases Application Application experience minimal downtime. servers 2 servers in a separate farm. servers servers · You can upgrade multiple content databases at the same time, which results in faster upgrade Upgrade multiple times overall than an in-place upgrade. databases in Content parallel. database · You can upgrade hardware in addition to software. 1-n 3 2 Read-only Content Database Database Database Database Database Database Database Database Database Database Database Database SSP database server 1 server 2 server 3 server A server B server C server 1 server 2 server 3 server A server B server C databases. database 1-n (content (services (config (content (services (config (content (services (config (content (services (config DBs) DBs) DB) DBs) DBs) DB) DBs) DBs) DB) DBs) DBs) DB) SSP Existing farm continues to serve New farm is built, then content Original farm is taken offline. New farm begins to process user database user requests, in read-only mode. databases are attached and requests. content is upgraded. Hybrid approach 2: Detach databases Hybrid techniques used Upgrade sequence Alternative upgrade sequence Original Original Original Visual Upgrade · Use an in-place upgrade to upgrade the farm and farm User farm 1 User 1 Take the original farm offline. 1 Set up a temporary small farm that is farm User requests requests Preview sites in the SharePoint 2010 settings. requests running the new version, and then Detach the content databases from Products look. Complete the change to the · Detach and upgrade multiple databases in 2 the original farm. take the original farm offline. SharePoint 2010 Products look when you parallel. 2 Detach the content databases from are ready. 3 Run an in-place upgrade on the the original farm. · Alternative upgrade sequence: Upgrade original farm servers, services, and 3 Run an in-place upgrade on the databases on a temporary small farm. configuration database. original farm. 4 Attach the content databases to the 4 Attach the content databases to the Advantages Disadvantages original farm and upgrade the content. Front-end Web servers Front-end Web servers temporary farm and upgrade them in Front-end Web servers parallel. · The existing farm settings are upgraded and do · Copying databases across the network takes time 3 5 Reattach the content databases to the not have to be manually transferred to a new farm. and bandwidth. You must plan for that. original farm. · You can upgrade multiple content databases at · You need direct access to the database servers. Application Application Application servers servers the same time, which results in faster upgrade servers Alternative upgrade sequence: times overall than an in-place upgrade. 2 Temporary small farm 1 User 2 Content 4 requests 4 database 1-n 5 Front-end Web Database Database Database Database Database Database Database Database Database server and server 1 server 2 server 3 server 1 server 2 server 3 server 1 server 2 server 3 application (content (services (config (content (services (config SSP (content (services (config server DBs) DBs) DB) DBs) DBs) DB) database DBs) DBs) DB) (complete) Upgrade multiple Database databases in parallel. Upgrade databases in a server Use an in-place upgrade to separate farm. upgrade the farm and settings. DRAFT Upgrade model 2 of 4 This document supports a preliminary release of Microsoft® SharePoint® 2010 Products. © 2009 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].