Download Slide 1

SharePoint Upgrade Deep Dive
Chandima Kulathilake
Solution Architect
Knowledge Cue
SESSION CODE: OFS308
Who am I?
Chandima – aka “Chan” @chandimak on twitter
Solutions Architect @ Knowledge Cue
- SharePoint Consulting in New Zealand
Started with SharePoint 2001... It’s been a great journey
SharePoint MVP since 2007
www.chandima.net/blog
[email protected]
3
Knowledge Cue
Help with strategy and planning for SharePoint
Sense making for large enterprise projects
Pre RFP stage expectation setting
SharePoint best practices/ “real world” balancing act
Consulting and deployment support
Microsoft certified SharePoint experts
@knowledgecue on twitter
www.knowledgecue.co.nz
4
Agenda
Getting your existing SharePoint 2003 > 2007 farm ready
for SharePoint 2010
Applying Software updates (Service Pack 2 and CU)
Testing your existing deployment for SharePoint 2010
readiness
Auditing what’s in your current deployment
Upgrade planning and upgrade tasks
What you can and can’t upgrade
Recommendations for SP2010
5
Upgrade Planning Cycle
Learn
Validate
Implement
6
Prepare
Test
Upgrade Paths
WSS2/SPS 2003 > SharePoint 2007 > SharePoint 2010
MCMS 2002 > SharePoint 2007 > SharePoint 2010
Project Server 2003 > Project 2007 > (SharePoint)
Project 2010
7
Getting Ready – Requirements
SharePoint Server 2010 and SharePoint Foundation
64-bit only
64-bit Windows Server 2008 SP2 or 64-bit Windows
Server 2008 R2
64-bit SQL Server 2008 SP1 + CU2 or CU5
64-bit SQL Server 2008 R2
Standard or Enterprise
PowerPivot needs SQL 2008 R2
64-bit SQL Server 2005 + SP3 and CU3 (Supported)
http://tinyurl.com/SP2010SysReqs
8
Move, Migrate or Upgrade
Move - Use the procedures for moving a farm or
components when you are changing to different
hardware (more capacity, performance and x64)
Migrate – From 32bit to 64bit or
SharePoint Content from 2003 to 2007 > 2010
Upgrade – Apply new updates and or Service Packs to
SharePoint Server 2007 or upgrade to SP2010
9
Preparing the servers
SQL Server (64bit)
SQL 2008 R2 or SQL 2008+SP1+CU2 (or greater)
SQL 2005 w/SP3 – supported / not recommended
SharePoint Servers (64bit)
SharePoint 2007 SP2 + October CU (or greater) – Recommend latest CU (June 2010)
October CU updates the preupgradecheck STSADM command
Windows Server 2008 Standard w/SP2 (or greater)
WCF Hot fix (not part of the prerequisites installer)
Plan for sufficient disk space – Upgrades will need temp disk
space (lots of)
10
Upgrade Planning
Evaluate – Where are you today?
Identify
Document
Plan
Review
Identify migration path to 64bit
Review future requirements
11
Auditing Tools for 2007 Farms
Central Administration in SharePoint
SharePoint Administration Toolkit V4.0 (SPDiag)
http://tinyurl.com/SPAdminKit
Using STSADM and PowerShell
Pre-Upgrade Check
Run the STSADM –o preupgradecheck command prior to upgrade (many times)
Run STSADM –o enumallwebs [parameters]
Using SharePoint Manager from Carsten Keutmann –
http://www.codeplex.com/spm
12
DEMO 1 - CONDUCTING A PREUPGRADE AUDIT
Using STSADM
STSADM –o enumcontentdbs
STSADM – o enumallwebs (SP 2 + Updates)
STSADM – o enumsolutions
STSADM – o preupgradecheck
14
Post Audit Tasks
Server Administrators – prepare servers and plan
SP2010 deployment architecture
Developers – Re-evaluate custom code solutions and
files for SP2010 compatibility
Project Managers – Review upgrade project plans and
estimates – user training etc.
15
VseWSS Upgrade Tool - Developers
16
Also Consider…
Move only “content” to brand new farm
Re-organise
Standardise
Clean up
Decommission – old hardware
17
Environment Cleanup
Spring cleaning for a healthy farm
Delete Stale Sites and Webs (Backup First )
stsadm -o DeleteSite [-force] [-gradualdelete]
stsadm -o DeleteWeb [-force]
Remove Extraneous Document Versions
Primarily user driven, OM operations or tools help
Cleanup Templates, Features, & Web Parts
Primarily user driven, OM operations or tools help
Repair Data Issues
stsadm -o DatabaseRepair [-deletecorruption]
stsadm -o ForceDeleteList
stsadm -o VariationsFixupTool
18
Upgrade Methods
19
In-Place Upgrade
Database Attach
Upgrade
Hybrid 1:
Hybrid 2:
Read-Only
Database Upgrade
Detach Database
Upgrade
In-Place Upgrade
Farm offline during upgrade
Configuration and all content upgraded
No option to roll-back (only if you backup the whole farm)
20
In-Place Upgrade
Install SharePoint Binaries on the Server with CA first
Run the Configuration Wizard
The SSP database is upgraded and data is copied into new user
profiles and taxonomy databases.
No option to roll-back (only if you backup the whole farm)
21
In-Place Upgrade
Very hard to predict – even if you test multiple times
Recommended for one-off tests only
Good for testing Code and extracting WSP solutions to Visual
Studio
ALL Databases will be GUID based
My recommendation – Don’t do it for a PRODUCTION
deployment!
22
DEMO 2 – IN PLACE UPGRADE
Database Attach Upgrade
New hardware and new farm for SP 2010
Install binaries first and configure required services
Re-deploy customisations (WSP files) manually
Attach content databases individually
24
Upgrade Sequence – Database Attach
Build new SP2010 farm
Create Web Application(s)
Detach content databases from
SP2007 farm
Attach content databases to
SP2010 farm
Test (repeat)
25
Database attach
New farm
http://contoso2
User
requests
Front-end Web servers
Application
servers
Content databases
SSP database
(Upgraded to User
Profiles_
26
Content
database 1-n
Database
Database
server A
server B
(content DBs) (services DBs)
SSP
database
Database
server C
(config DB)
DEMO 3 – DATABASE ATTACH UPGRADE
Database Attach – What you Get
Chance to re-organise
Remove unwanted sites
Phased upgrades
Plan your Service Applications properly
28
Using PowerShell
Test-SPContentDatabase -Name -WebApplication [AssignmentCollection ] [-DatabaseCredentials ] [ServerInstance ]
Test-SPContentDatabase -Name My_Content_DB –
Webapplication http://portal.abc.com
29
Test-SpContentDatabase
30
Mount-SPContentDatabase
31
Upgrade – HYBRID Approaches
Hybrid 1 – Read only databases
Set content databases to read-only in SQL server
32
Upgrade – HYBRID Approaches
Hybrid 2 – Detach databases
Detach all content databases
Run in place upgrade and update farm
binaries to SP2010
Configure required Service Applications
Attach each content database individually
33
34
Upgrade – What to do for Developers
Covert your custom code to deployable solutions
http://tinyurl.com/SP2010Solutions
Visual Studio 2010 support for SharePoint 2010
development
Follow Coding Best Practices
http://tinyurl.com/CodingBPSP07
Download SP2010 SDK
http://tinyurl.com/SP2010DEVSDK
35
Upgrade – What to do for Administrators
Large content databases and site collections will take longer
to upgrade
Split Content Databases and/or Site Collections into smaller
units prior to upgrade
STSADM’s mergecontentdbs command can be used to move
a Site Collection to a different Content Database
Gary Lapointe’s convert sub site to site collection command
Archive off any Site Collections, Webs, or Lists that are no
longer necessary
Test your Disaster Recovery strategy before upgrading
36
Upgrade Gotchas
3rd Party vendor solutions – custom development
3rd Party products – Aggregation web parts or similar
Forgotten sites with no owners
37
Migration strategies
SOURCE (32bit) FARM A
DESTINATION (64bit) FARM B
Tier C – Phase 3
x86 (MOSSWEB1) x86 (MOSSWEB2)
x64 (SPWEB1) x64 (SPWEB2)
Tier B – Phase 2
x86 (MOSSAPP1)
x64 (SPAPP1)
Tier A – Phase 1
x86 (SQL)
38
x64 (SQLSERVER08)
Resources
Upgrade Resource Centre (TechNet)
http://tinyurl.com/SP2010Upgrade
Upgrade planning blog post series
http://tinyurl.com/SP2010Blogs
47
Announcing – SharePoint Day
A Business Track – Hosted by Mark Orange (4 sessions)
A Technical Solution Track – Hosted by Chandima
Kulathilake (4 sessions)
Where : Hotel Intercontinental – Wellington
When : September 29th 9.00am onwards
Email : [email protected] to register your
interest
Cost : NONE!
48
Thank you
Q and A – Meet me outside or
[email protected]
Lots of improvements – Features solutions
Lots of complexity – Architecture and Planning
“with great power comes greater responsibility”
49
© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should
not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS,
IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.