SharePoint 2010 Migration Presentation

3,312 views
3,195 views

Published on

SharePoint 2010 Migration Presentation

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,312
On SlideShare
0
From Embeds
0
Number of Embeds
350
Actions
Shares
0
Downloads
231
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • # After the server administrator performs all pre-upgrade steps, the administrator runs Setup for SharePoint Server 2010 on the server that hosts the SharePoint Central Administration Web site. Because the previous version was installed, an in-place upgrade is automatically selected.# After Setup runs on the server that hosts the Central Administration Web site, the server administrator runs Setup on the remaining front-end Web servers and application servers in the farm.# The server administrator runs the SharePoint Products and Technologies Configuration Wizard on the server that hosts the Central Administration Web site. This server, the configuration database, the services, and the content databases are upgraded sequentially.When the configuration wizard finishes, the Central Administration Web site opens. A timer job schedules the upgrade process to run for each site collection. The upgrade process timer job upgrades each site collection. After all sites are upgraded, the upgrade process ends.# The server administrator runs the SharePoint Products and Technologies Configuration Wizard on all the other servers in the farm.
  • A database attach upgrade enables you to move to new hardware or a new farm. During a database attach upgrade, you detach all the content databases from an existing farm and then attach the databases to a new server farm installation. When you attach the databases to the new server farm, the upgrade process runs and upgrades the data in place.The following steps explain what happens during a database attach upgrade:The server administrator sets up and configures a new SharePoint Server 2010 farm. The administrator transfers all customizations to the new farm and tests the environment.For more information about configuring the new environment, see Prepare the new SharePoint Server 2010 environment for a database attach upgrade.The server administrator detaches the content databases from the old Office SharePoint Server 2007 farm and takes the old farm offline (for example, by changing the load balancer or IIS Web applications to stop service requests, or by turning off all of the components and services on each server computer in the farm).The server administrator attaches the content databases to the new farm and upgrades the content.The server administrator confirms that the upgrade has finished successfully and then configures the new farm to start serving requests at the new URL.
  • This approach gives users continuous read-only access to their data while you are upgrading. The content databases in the original farm are set to read-only, and copies of the databases are upgraded on a new farm. The following steps explain what happens during a database attach upgrade with read-only databases:The server administrator sets up and configures a new SharePoint Server 2010 farm. The administrator transfers all customizations to the new farm and tests the environment.The server administrator changes the content databases to read-only. The administrator then uses SQL Server to back up the content databases on the Office SharePoint Server 2007 farm and restore them to the new farm.The server administrator attaches the new copies of the content databases, and the upgrade process runs and upgrades the content.After the upgrade process runs, the server administrator confirms that the upgrade has finished successfully. The administrator then configures the new farm to start serving requests at the new URL and takes the original farm offline (for example, by changing the load balancer or IIS Web applications to stop service requests, or by turning off all of the components and services on each server computer in the farm).
  • This approach enables you to speed up the upgrade process by detaching and attaching databases to upgrade multiple databases at the same time. It is an in-place upgrade because you are upgrading the original farm; however, you can also use another farm to perform the upgrade and then attach the upgraded databases to your original farm. Note that the original farm cannot serve requests during the upgrade process. As in a standard in-place upgrade, users cannot access their content while the upgrade is in progress.The following steps explain what happens during an in-place upgrade with detached databases:The server administrator takes the original farm offline (for example, by changing the load balancer or IIS Web applications to stop service requests, or by turning off all of the components and services on each server computer in the farm).The server administrator detaches the content databases from the original farm.The server administrator runs an in-place upgrade on the original farm servers, services, and configuration database.The server administrator attaches the content databases to the original farm and upgrades the content.Alternatively, you can use a separate, temporary small farm to perform the upgrade. In this approach, you attach the databases to the original farm after they have been upgraded.The following steps explain what happens during an in-place upgrade with detached databases and a temporary small farm to upgrade the content databases:The server administrator sets up a temporary small farm that is running the new version. Then the administrator takes the original farm offline (for example, by changing the load balancer or IIS Web applications to stop service requests, or by turning off all of the components and services on each server computer in the farm).The server administrator detaches the content databases from the original farm.The server administrator runs an in-place upgrade on the original farm to upgrade the servers, services, and configuration database.The server administrator attaches the content databases to the temporary small farm and upgrades them in parallel.The server administrator reattaches the content databases to the original farm.The server administrator confirms that the upgrade has finished successfully.If Visual Upgrade is being used, the server administrator or site owner previews sites in the Microsoft SharePoint Server 2010 look. When the administrator or site owner is ready, he or she completes the change to the Microsoft SharePoint Server 2010 look.
  • This approach enables you to speed up the upgrade process by detaching and attaching databases to upgrade multiple databases at the same time. It is an in-place upgrade because you are upgrading the original farm; however, you can also use another farm to perform the upgrade and then attach the upgraded databases to your original farm. Note that the original farm cannot serve requests during the upgrade process. As in a standard in-place upgrade, users cannot access their content while the upgrade is in progress.The following steps explain what happens during an in-place upgrade with detached databases:The server administrator takes the original farm offline (for example, by changing the load balancer or IIS Web applications to stop service requests, or by turning off all of the components and services on each server computer in the farm).The server administrator detaches the content databases from the original farm.The server administrator runs an in-place upgrade on the original farm servers, services, and configuration database.The server administrator attaches the content databases to the original farm and upgrades the content.Alternatively, you can use a separate, temporary small farm to perform the upgrade. In this approach, you attach the databases to the original farm after they have been upgraded.The following steps explain what happens during an in-place upgrade with detached databases and a temporary small farm to upgrade the content databases:The server administrator sets up a temporary small farm that is running the new version. Then the administrator takes the original farm offline (for example, by changing the load balancer or IIS Web applications to stop service requests, or by turning off all of the components and services on each server computer in the farm).The server administrator detaches the content databases from the original farm.The server administrator runs an in-place upgrade on the original farm to upgrade the servers, services, and configuration database.The server administrator attaches the content databases to the temporary small farm and upgrades them in parallel.The server administrator reattaches the content databases to the original farm.The server administrator confirms that the upgrade has finished successfully.If Visual Upgrade is being used, the server administrator or site owner previews sites in the Microsoft SharePoint Server 2010 look. When the administrator or site owner is ready, he or she completes the change to the Microsoft SharePoint Server 2010 look.
  • This approach enables you to speed up the upgrade process by detaching and attaching databases to upgrade multiple databases at the same time. It is an in-place upgrade because you are upgrading the original farm; however, you can also use another farm to perform the upgrade and then attach the upgraded databases to your original farm. Note that the original farm cannot serve requests during the upgrade process. As in a standard in-place upgrade, users cannot access their content while the upgrade is in progress.The following steps explain what happens during an in-place upgrade with detached databases:The server administrator takes the original farm offline (for example, by changing the load balancer or IIS Web applications to stop service requests, or by turning off all of the components and services on each server computer in the farm).The server administrator detaches the content databases from the original farm.The server administrator runs an in-place upgrade on the original farm servers, services, and configuration database.The server administrator attaches the content databases to the original farm and upgrades the content.Alternatively, you can use a separate, temporary small farm to perform the upgrade. In this approach, you attach the databases to the original farm after they have been upgraded.The following steps explain what happens during an in-place upgrade with detached databases and a temporary small farm to upgrade the content databases:The server administrator sets up a temporary small farm that is running the new version. Then the administrator takes the original farm offline (for example, by changing the load balancer or IIS Web applications to stop service requests, or by turning off all of the components and services on each server computer in the farm).The server administrator detaches the content databases from the original farm.The server administrator runs an in-place upgrade on the original farm to upgrade the servers, services, and configuration database.The server administrator attaches the content databases to the temporary small farm and upgrades them in parallel.The server administrator reattaches the content databases to the original farm.The server administrator confirms that the upgrade has finished successfully.If Visual Upgrade is being used, the server administrator or site owner previews sites in the Microsoft SharePoint Server 2010 look. When the administrator or site owner is ready, he or she completes the change to the Microsoft SharePoint Server 2010 look.
  • SharePoint 2010 Migration Presentation

    1. 1. Migrate to SharePoint 2010 – Stress Free!<br />Nick Kellett, CTO<br />
    2. 2. Agenda<br />A Little History<br />Common Migration Pains<br />SharePoint 2010 Technical Changes<br />Governance<br />Migration Options<br />Migration Tools and Utilities<br />The Migration Process<br />Recommendations<br />
    3. 3. A Little History<br />2003 to 2007 Migration<br />Options: In Place, Gradual, Database Migration<br />Common problems: <br />Customizations and unghostedPages<br />Architecture changes<br />OOTB migration wasn’t granular enough<br />Third party tools<br />
    4. 4. Common Migration Problems<br />
    5. 5. SharePoint Technical Changes<br />Hardware Requirements<br />64x Architecture<br />Windows Server 2008 or Windows Server 2008 R2 64x<br />SQL Server 2005 SP3 or SQL Server 2008 SP1 64x<br />Architecture Changes<br />Service Applications – No more SSP!<br />Sandboxed Solutions<br />SharePoint Designer<br />STSAdm out, PowerShell in<br />No Internet Explorer 6 Support<br />
    6. 6. Governance<br />
    7. 7. SharePoint Governance<br />Centralized thought process<br />Structured approach to building and managing SharePoint<br />Provides staff with appropriate tools, training, support, and information<br />Characteristics:<br />Organization-specific<br />Team-driven: Governance Team, Tactical Teams<br />Disciplined and results-oriented approach<br />Requires good communication<br />
    8. 8. Governance Requirements<br />Governance Site<br />Communications<br />Policies and Procedures<br />Training<br />Support<br />Taxonomy<br />Project Schedule<br />Communication<br />Support<br />Training<br />
    9. 9. Best Practices<br />Ideally Governance Predates SharePoint<br />Build a Governance Portal<br />Communicate Frequently <br />Identify and Support Champions<br />Evergreen your process<br />
    10. 10. Migration Options<br />
    11. 11. Migration Options<br />Types of Migration:<br />Content / Data<br />Functionality<br />Content Migration Options<br />In Place<br />Database Attach<br />Hybrid<br />Option 1 - Read-only Databases<br />Option 2 - Parallel Databases<br />
    12. 12. Migration Options – In Place<br />Upgrades your existing farm (if 64x)<br />Run Setup for SharePoint Server 2010 on Central Admin server<br />Run Setup on WFE and Application Servers<br />Run the SharePoint Products and Technologies Configuration Wizard on Central Admin to update config db, services, content dbs. Timer updates all site collections<br />Run Configuration Wizard on WFE and Application Servers<br />
    13. 13. Migration Options – Database Attach<br />Install new 2010 Farm<br />Detach all content databases<br />Take old farm offline<br />Attach content databases to new 2010 farm<br />Automatic upgrade process occurs<br />
    14. 14. Migration Options – Hybrid 1<br />Database Attach with Read-only Databases<br />Setup 2010 Farm<br />Transfer all functionality to 2010 and test<br />Set 2007 content databases to Read-only<br />Detach content databases using SQL Server<br />Attach to 2010 Farm to get automatic upgrade<br />Test upgrade<br />Configure 2010 Farm to serve requests<br />Take 2007 Farm offline<br />
    15. 15. Migration Options – Hybrid 2<br />In-Place with Detach Databases<br />Detach content databases<br />Perform In-Place upgrade on existing 2007 farm and config database<br />Re-attach content databases to 2010 Farm to get automatic upgrade<br />Test upgrade<br />
    16. 16. Migration Options – Pros and Cons<br />In-Place <br />PRO: Does not require new hardware<br />PRO: Uses Existing Farm configurations<br />CON: Cannot serve requests from original farm<br />CON: No way to reverse if something goes wrong<br />Attach Databases<br />PRO: Can serve requests from 2007 farm while migration occurs<br />PRO: Can update multiple databases at once<br />PRO / CON: Requires new 2010 Farm and hardware<br />PRO / CON: You have to setup new Farm Configuration Settings<br />CON: Risk of new content being added to old Farm mid-migration<br />
    17. 17. Migration Options – Pros and Cons (cont.)<br />Hybrid 1 – Read-only Databases<br />PRO / CON: Requires new 2010 Farm and hardware<br />PRO: Can serve requests from existing farm<br />PRO: No risk of content being added mid-migration<br />CON: Prevents content from being updated until migration complete<br />Hybrid 2 – Detach Databases (In Place With Database Detach)<br />CON: Cannot serve requests from original farm<br />PRO: Does not require new hardware<br />PRO: Can upgrade multiple databases at once for faster upgrade <br />
    18. 18. Migration Options – Functionality<br />Feature Upgrade<br />Do you need old functionality?<br />Recompile custom code to 64x if possible<br />Third Party Products<br />
    19. 19. Migration Options – Tools & Utilities<br />Preupgrade check<br />PowerShelltest-spcontentdatabasecmdlet<br />Visual Upgrade<br />Major Vendors migration tools<br />Administrator and Vendor Utilities<br />
    20. 20. Migration Process<br />
    21. 21. Migration Process<br />Restructure Farm?<br />Pre-Migration Checklist<br />1…n Test Migrations<br />Production Migration<br />Final steps<br />
    22. 22. Restructuring<br />This is a good opportunity to restructure your farm<br />Use mergedb to consolidate site collections into one content database<br />Use backup / restore to move site collections around<br />Use Third Party Tools to restructure:<br />Web Application, Site Collections, and Site Layouts<br />Navigation<br />Content <br />
    23. 23. Migrate to 64x<br />
    24. 24. Pre-Migration Checklist<br />(If not already using 64x)<br />Provision 64x Hardware<br />Setup Windows Server 2008 x64<br />Setup SQL Server 2008 or 2005 SP2 x64<br />Migrate SharePoint 2007 32x to 64x <br />Upgrade SharePoint 2007 to SP2<br />Run preupgrade checker on 2007<br />Backup All Databases<br />Install All 2010 Prerequisites<br />
    25. 25. Pre-Upgrade Checker<br />STSADM.EXE -o preupgradecheck [[-rulefiles "rule file name"] | [-listrulefiles]] [-localonly]<br />The Checker Lists:<br />All servers and components in the farm<br />Whether the servers and db can be upgraded<br />Alternate access mapping URLs<br />Site definitions, site templates, features, language packs<br />Missing or invalid configuration (such as Web.config file, invalid host names, or invalid service accounts)<br />Unsupported farm customizations (such as database schema modifications)<br />Database or site orphans<br />
    26. 26. 1..n Test Migrations<br />Setup Test environment<br />Create database copy of real content<br />Migrate using the chosen approach<br />Check the Log Files<br />%COMMONPROGRAMFILES%Microsoft SharedWeb server extensions14LOGS<br />PSCDiagnostics_<br />Upgrade- .log and .err files<br />Test Data and Functionality<br />Test Visual Upgrade on site collections<br />Identify and fix problems<br />
    27. 27. 1..n Test Migrations<br />Setup Test environment<br />Create database copy of real content<br />Migrate using the chosen approach<br />Check the Log Files<br />%COMMONPROGRAMFILES%Microsoft SharedWeb server extensions14LOGS<br />PSCDiagnostics_<br />Upgrade- .log and .err files<br />Test Data and Functionality<br />Test Visual Upgrade on site collections<br />Identify and fix problems<br />
    28. 28. Migration Fixes<br />Turn off features or functionality you don’t need<br />Delete orphans<br />stsadm -o databaserepair -url http://<URL_of_WindowsSharePointServices_Site> -databasename <name of database that contains the orphan item> [-deletecorruption]<br />To view status of each web app:stsadm -o localupgradestatuson each web app<br />To resume upgrade on skipped web apps:PowerShellupgrade-spcontentdatabase -id <GUID><br />
    29. 29. Migration Fixes<br />Turn off features or functionality you don’t need<br />Delete orphans<br />stsadm -o databaserepair -url http://<URL_of_WindowsSharePointServices_Site> -databasename <name of database that contains the orphan item> [-deletecorruption]<br />To view status of each web app:stsadm -o localupgradestatuson each web app<br />To resume upgrade on skipped web apps:PowerShellupgrade-spcontentdatabase -id <GUID><br />
    30. 30. Migration Production<br />Setup production environment<br />Migrate using the chosen approach<br />Test Data<br />Test Functionality<br />Use Visual Upgrade on site collections<br />Switch over requests to new farm (if required)<br />
    31. 31. Migration Recommendations<br />Plan and Govern Early<br />Audit your content and functionality<br />Consider restructuring<br />Virtualize<br />Build SharePoint 2010 Farm for testing<br />Test with copy of real content <br />Deploy all functionality to test farm<br />Preferred Option: Hybrid Migration – Read-only Databases<br />“Best of the worst” options: Hybrid 2 – Parallel Database Detach<br />
    32. 32. Wrapup<br />
    33. 33. Migration Resources<br />Upgrade and Migration Resource Center for Microsoft SharePoint Server 2010 (http://technet.microsoft.com/en-us/sharepoint/ee517214.aspx)<br />Jie Li’s Blog: Upgrade Prerequisites Links: (http://blogs.msdn.com/opal/archive/2009/10/25/sharepoint-2010-pre-requisites-download-links.aspx)<br />Migrating an Existing 2007 Farm to 64x: (http://technet.microsoft.com/en-us/library/dd622865.aspx?ppud=4) <br />
    34. 34. Questions?<br />Email: nkellett@stoneshare.com<br />Blog: http://planetmoss.blogspot.com<br />www.linkedin.com/in/nicholaskellett<br />www.stoneshare.com<br />
    35. 35. Thank You!<br />www.stoneshare.com<br />

    ×