SharePoint 2010 Migration Presentation
Upcoming SlideShare
Loading in...5
×
 

SharePoint 2010 Migration Presentation

on

  • 3,776 views

SharePoint 2010 Migration Presentation

SharePoint 2010 Migration Presentation

Statistics

Views

Total Views
3,776
Views on SlideShare
3,444
Embed Views
332

Actions

Likes
2
Downloads
218
Comments
0

25 Embeds 332

http://planetmoss.blogspot.com 169
http://stonesharepoint.blogspot.com 73
http://planetmoss.blogspot.in 24
http://stonesharepoint.blogspot.ca 20
http://planetmoss.blogspot.ca 13
http://planetmoss.blogspot.com.au 4
http://stonesharepoint.blogspot.co.uk 3
http://planetmoss.blogspot.co.uk 3
http://feeds.feedburner.com 2
http://planetmoss.blogspot.fr 2
http://stonesharepoint.blogspot.hk 2
http://stonesharepoint.blogspot.de 2
http://www.slideshare.net 2
http://stonesharepoint.blogspot.fr 2
http://stonesharepoint.blogspot.be 1
http://planetmoss.blogspot.it 1
http://planetmoss.blogspot.co.nz 1
http://stonesharepoint.blogspot.com.au 1
http://planetmoss.blogspot.dk 1
http://planetmoss.blogspot.sg 1
http://stonesharepoint.blogspot.ro 1
http://stonesharepoint.blogspot.co.il 1
http://planetmoss.blogspot.fi 1
http://translate.googleusercontent.com 1
http://planetmoss.blogspot.pt 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • # 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 SharePoint 2010 Migration Presentation Presentation Transcript

  • Migrate to SharePoint 2010 – Stress Free!
    Nick Kellett, CTO
  • Agenda
    A Little History
    Common Migration Pains
    SharePoint 2010 Technical Changes
    Governance
    Migration Options
    Migration Tools and Utilities
    The Migration Process
    Recommendations
  • A Little History
    2003 to 2007 Migration
    Options: In Place, Gradual, Database Migration
    Common problems:
    Customizations and unghostedPages
    Architecture changes
    OOTB migration wasn’t granular enough
    Third party tools
  • Common Migration Problems
  • SharePoint 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
  • Governance
  • 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
  • Governance Requirements
    Governance Site
    Communications
    Policies and Procedures
    Training
    Support
    Taxonomy
    Project Schedule
    Communication
    Support
    Training
  • Best Practices
    Ideally Governance Predates SharePoint
    Build a Governance Portal
    Communicate Frequently
    Identify and Support Champions
    Evergreen your process
  • Migration Options
  • 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
  • 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 Configuration Wizard on WFE and Application Servers
  • Migration Options – Database Attach
    Install new 2010 Farm
    Detach all content databases
    Take old farm offline
    Attach content databases to new 2010 farm
    Automatic upgrade process occurs
  • 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
  • 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
  • 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
  • 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
  • Migration Options – Functionality
    Feature Upgrade
    Do you need old functionality?
    Recompile custom code to 64x if possible
    Third Party Products
  • Migration Options – Tools & Utilities
    Preupgrade check
    PowerShelltest-spcontentdatabasecmdlet
    Visual Upgrade
    Major Vendors migration tools
    Administrator and Vendor Utilities
  • Migration Process
  • Migration Process
    Restructure Farm?
    Pre-Migration Checklist
    1…n Test Migrations
    Production Migration
    Final steps
  • 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
  • Migrate to 64x
  • Pre-Migration Checklist
    (If not already using 64x)
    Provision 64x Hardware
    Setup Windows Server 2008 x64
    Setup SQL Server 2008 or 2005 SP2 x64
    Migrate SharePoint 2007 32x to 64x
    Upgrade SharePoint 2007 to SP2
    Run preupgrade checker on 2007
    Backup All Databases
    Install All 2010 Prerequisites
  • Pre-Upgrade Checker
    STSADM.EXE -o preupgradecheck [[-rulefiles "rule file name"] | [-listrulefiles]] [-localonly]
    The Checker Lists:
    All servers and components in the farm
    Whether the servers and db can be upgraded
    Alternate access mapping URLs
    Site definitions, site templates, features, language packs
    Missing or invalid configuration (such as Web.config file, invalid host names, or invalid service accounts)
    Unsupported farm customizations (such as database schema modifications)
    Database or site orphans
  • 1..n Test Migrations
    Setup Test environment
    Create database copy of real content
    Migrate using the chosen approach
    Check the Log Files
    %COMMONPROGRAMFILES%Microsoft SharedWeb server extensions14LOGS
    PSCDiagnostics_
    Upgrade- .log and .err files
    Test Data and Functionality
    Test Visual Upgrade on site collections
    Identify and fix problems
  • 1..n Test Migrations
    Setup Test environment
    Create database copy of real content
    Migrate using the chosen approach
    Check the Log Files
    %COMMONPROGRAMFILES%Microsoft SharedWeb server extensions14LOGS
    PSCDiagnostics_
    Upgrade- .log and .err files
    Test Data and Functionality
    Test Visual Upgrade on site collections
    Identify and fix problems
  • 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>
  • 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>
  • 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)
  • Migration 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 – Parallel Database Detach
  • Wrapup
  • 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)
  • Questions?
    Email: nkellett@stoneshare.com
    Blog: http://planetmoss.blogspot.com
    www.linkedin.com/in/nicholaskellett
    www.stoneshare.com
  • Thank You!
    www.stoneshare.com