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