SharePoint Upgrade Scenarios

Quick Facts

About Us• 22nd Year• Grand Rapids &

Royal Oak• 30 Staff

Approach• Vendor

Independent• Non-reseller• Professional

Services Only

Partnerships• Microsoft Gold• VMware Enterprise• Citrix Silver• Cisco Registered• Novell Gold

Expertise

Get Social with C/D/H

C/D/H Talks Tech C/D/H Tweets Tech

About me

Julie BoudroConsultantMCITP, MCTS, MCTjulieb@cdh.com248.554.3176

Overview

• Determining your upgrade approach• Preparing your upgrade approach• Troubleshooting upgrade failures• Cut-over strategies

Determine your upgrade approach

• In-place upgrade– Development environment only

• Database attachment– Production environments– Ideal for minimal farm-level configurations

• Hybrid approach(es)– Read-only with a secondary farm– Detach database with in-place upgrade

In-place upgrade

Pros ConsGreat for development environment

Difficult to revert back to previous environment

Upgrades entire environment including Central Admin, SSP and sites

Farm is unavailable while the upgrade is running

Limited control over the naming conventions for 2010 databasesServers must be running Windows Server 2008 (R2)

Database attachment upgrade

Pros ConsGreat for environments with little farm-level configuration

Farm configurations are not upgraded from old environment

Ability to perform a test upgrade Shared Service Provider database is not automatically upgraded

Clean install of SharePoint 2010 Requires a “content freeze” for the final production upgrade

Minimal downtime for end users If moving to a new SQL environment, databases must be copied over the network

Easy recovery in case of a failure

Hybrid option #1: Database attach with read-only databases

Pros ConsExisting farm can be accessed while the upgrade is occurring on another farm

Existing farm is read-only

Ability to upgrade multiple site collections / databases at the same time

Farm configurations are not upgraded from old environment

Minimal downtime to users Shared Service Provider database is not automatically upgraded

Easy recovery in case of failure Must copy databases over the network if moving to a new SQL environment

Hybrid option #2: In-place upgrade with database attach

Pros ConsFarm-wide configuration settings are upgraded

Hardware must be able to support SharePoint 2010

Database attachment supports the flexibility of upgrading multiple sites which increases overall upgrade time

Farm is unavailable during the upgrade process

Preparing your upgrade approach

Component Minimum requirement Processor 64-bit, four cores

RAM4 GB for developer or evaluation use8 GB for production use in a single server or multiple server farm

Hard disk 80 GB for system drive

Software

Windows Server 2008 R2SQL Server 2005 with SP2 orSQL Server 2008 R2 orSQL Server 2012

http://technet.microsoft.com/en-us/library/cc262485.aspx#section4

Hardware / Software Requirements

Preparing your environment

• SharePoint 2003 > SharePoint 2007 SP2• SharePoint 2007 SP2• Pre-upgrade checker

– Alternate access mapping settings– Installed elements– Unsupported customizations – Orphaned objects – Valid configuration settings– Database requirements

Preparing your environment

• Locate custom code• Clean house

– Site collections– Third-party tools– Large databases– Document versions

Troubleshooting upgrade failures

Known Upgrade Issues– Microsoft FAB 40 templates– Customizations– Custom site definitions

Other Issues– Missing customizations– Security and permissions– Lack of space

Cutover strategies

• Communication plan• Trial upgrade • Test upgraded environment• Test visual upgrade• Content freeze• Production upgrade • Support

Conclusion

• Determine the impact of an upgrade in your environment

• Have a solid plan• Test, test, test• Post upgrade support plan

Royal Oak306 S. Washington Ave.Suite 212Royal Oak, MI 48067p: (248) 546-1800

Thank You

Grand Rapids15 Ionia SWSuite 270Grand Rapids, MI 49503p: (616) 776-1600

(c) C/D/H 2007. All rights reservedwww.cdh.com