26
André J. Heymann | June 20 th , 2007 Upgrading to SharePoint 2007
André J. Heymann | June 20th, 2007
Upgrading to SharePoint 2007
Agenda
• The SharePoint Basics
• The Microsoft Internal Upgrade To MOSS– Deployment Overview
– SharePoint 2003 and SharePoint 2007 Architecture
• Upgrade Options Explained / Pro’s and Con’s– In-place Upgrade
– Gradual Upgrade
– Database Migration
• The Best Practices
2
Please! Ask Lots of Questions!!
3
ConfigDB
SharePoint Farm 1
4
Web
List
List
Web
WebWeb
Site CollectionWeb
List
List
Web
WebWeb
Site CollectionWeb
List
List
Web
WebWeb
Site Collection
Web Application (Portal)
ContentDatabases
Farm 2
Farm 3
Farm 4
Let‘s talk SharePoint Vocabulary
SharedServices
SSP DB
Search DB
How does the Microsoft upgrade compare to yours
Think about your Current/Planned
Sharepoint Deployment….
1 Farm, 1 Portal and a few sites…
5
…wasn‘t quite that simple
Microsoft SharePoint 2003 Deployment
• ~ 12 TB of Content, 110‘000 Site Collections (Portal, Collaborative and Personal Sites), 330‘000 Webs
• ~ 100 Servers– WSSv2- / SPS2003 Front-End‘s, Search, Index,
SQL2000/SQL2005
– ~ 90‘000 unique users (10‘000 extranet)
• 20+ Farms / Deployed in 3 Locations World Wide– Redmond, Dublin, Singapore
• Managed Centrally from one Team in Redmond/USA– Operations, Engineers, Program Managers, Service Managers
6
Pre / Post Upgrade SharePoint Architecture
7
SharePoint 2003 Architecture(Redmond)• Master Portal (Parent Farm)
• Provides Shared Services (Profiles, Audiences, Search, Alerts)
• Microsoft Intranet• Personal Sites
• Child Farms (Consumer)• Not Customized Portals• Customized Portals
• WSS (does not consume)• Team Collaborative Farm• Host Header Collab. Farm
Farm 1 / NLB
WSS Collaborative Farms
SharePoint 2003 Architecture
8
Index TargetFront-End Server / Load Balanced
Index ServersI I I
SearchServersS S
SQL Cluster
Farm 1 / NLB
Farm 2 / NLB
Shared Service Providing Parent FarmMicrosot Web / Personal Sites
Child Portal FarmsCustom / Vanilla
Farm 1 / NLB
WSS Collaborative Farms
SharedServices
SharePoint 2003 Challanges
• Microsoft Web and Personal Sites are of different nature but are on the same Portal
• Customization impacts each other
• Shared Services can affect availability
• Not transparent - adds complexity
9
In such large and complex deployments, you really want to keep your major
portal to itself….
Pre / Post Upgrade SharePoint Architecture
10
SharePoint 2003 Architecture(Redmond)• Master Portal (Parent Farm)
• Provides Shared Services (Profiles, Audiences, Search, Alerts)
• Microsoft Intranet• Personal Sites
• Child Farms (Consumer)• Not Customized Portals• Customized Portals
• WSS (does not consume)• Team Collaborative Farm• Host Header Collab. Farm
SharePoint 2007 Architecture(Redmond)• Shared Services Farm (Parent Farm)
• Shared Services Provider(Profiles, Audiences, Search,
Analytics, Business Data Catalogue)
• Child Farms (Consumer)• Microsoft Intranet• Personal Sites• Collaborative Sites MOSS• WSSv3 Farms -> MOSS• Departmental Farms
SharePoint 2007 Architecture
Front-End / Query Servers
Index ServerI
Shared Service Provider
Shared Service Provider
Front-End / Query Servers
Excel ServicesE
Personal Sites / Collab.
Front-End / Query Servers
Excel ServicesE
Departmental Portals
Front-End / Query Servers
Excel ServicesE
Microsoft Web
Benefits Of New SharePoint 2007 Architecture
• Shared Services On Dedicated Farm– Troubleshooting SSP Does Not Affect Other Portals (Most Cases)
– Dedicated SSP Recommended For Large Deployments
• Microsoft Intranet And Personal Sites Separated– No Issues With Customization Deployment Schedules
– No Personal Site Web Part Information Saved In Master Portal
• Roles And Responsibilities Mapped To Farms
• Easy To Add Additional Custom Farms
• Benefits Managing BDC Definitions / Global Forms
12
Let’s Talk Upgrade:What Are Your Upgrade Options And
Which One To Choose?
13
Three Upgrade uptions…but be creative..
• In-place– One Click Microsoft Magic
• Database Migration– Take Your v2 Content Database And Attach It To v3
• Gradual Upgrade– Upgrade Site Collection One At A Time
14
Gradual Upgrade
Advantages
15
Disadvantages
• Wssv3/MOSS Must Be Installed On Wssv2/SPS2003 Farm
• Client Redirect
• Does Require Additional Disk space (2+ Times In Most Scenarios)
• Worse Upgrade Performance Than Database Migration
• Time Intense Trial-run Preparation
• Granularity On Site Collection Level
• Fail-back To V2 Site Collection Possible
• Only Site Collections Being Upgraded Down
• Upgrades Some Customization (Webparts)
• You Can Choose When To Upgrade What (Custom Site Definitions?)
Gradual Upgarde
16
SharePoint 2003 and SharePoint 2007are running on the
same hardware!
Config DBVersion 3
Config DB Version 2
Prof_ Serv_
SQL Server
Site_ / ContentProf_ Serv_ Site_ / Content SSP SearchContent
WSS Upgrade TempDB
Demo Gradual Upgrade
17
Database Migration
Advantages
18
Disadvantages
• Requires Additional Hardware (Most Of The Time)
• You Usually Have To Upgrade The Entire Hostname
• Fallback Entire Farm Or Restore Content Database
• Does Not Upgrade Customization (You Need To Handle This)
• Does Not Upgrade Search Settings
• V2 Environment Is Not Affected By Upgrade
• Content Database Is The Granularity (No Confusion What Has Been Upgraded)
• Does Not Require Additional Disk space
• Best Upgrade Performance
• Easy To Do Trial Runs• Preferred Method For
Scalable Hosting Mode V2 Farms
Database Migration
19
Version 2 Version 3
Config DBVersion 3
Config DB Version 2
Prof_ Serv_ Site_ / Content
SQL Server
SSP SearchDB
SharePoint 2003 SharePoint 2007
Best Practices - Planning
• Decide On Upgrade Approach
• Define Service Offering– What Services/Features Will Be Offered
– What Training Is Required
– What‘s The Communication Strategy
• Architect Shared Service Provider
• Plan For Additional Storage During Upgrade– Especially When You Do Gradual Upgrades
• Identify Custom Site / List Definitions– Redo Using V3 Features
– Write Upgrade Definitions
20
Best Practices - Planning
• Identify Language Packs
• Define Ghosting/Un-Ghosting Strategy
• Consider To Upgrade To SQL 2005 (Optional)
• Understand Your Search Strategy. MOSS And WSS Search Are Different
• Understand Impact Of Gradual Upgrade Approach -URL Redirect
• Write Lock Upgraded V2 Site Collections / Portals
• Plan For V2 Restore Infrastructure
21
Best Practices - Preperation
• Run Prescan /All– Run Prescan 2 Weeks Before Upgrade
– Run Prescan Again 24hrs Before Upgrade
– Prescan Will Change The Last Modified Attributed
• Clean-up Config And Content Database Orphans
• Consider Splitting Large Content Databases (Sharepoint User Utility Suite 2.5)
• Consider Distributing SQL Databases Across Several SQL Backend (Helps With A Lot Of Data)
• Do Dry Run – Familiarize With The Upgrade and Upgrade Performance
22
Best Practices – Upgrade Performance
At Beta 2, The Following Upgrade Performance Was Measured:
•15 – 30 GB/Hrs WSS Gradual Upgrade / MOSS Upgrades Will Be Slower
•50 – 60 GB/Hrs WSS Database Migration / MOSS Upgrades Will Be Slower
•Performance Is A Measure Of # Of Lists, # Of Sites, # Of Web And Marginally Content Size
•SharePoint 2003 To MOSS Upgrades Are Slower Because Of Additional Features
23
Best Practices – Upgrade Execution
• Understand Where Your _Pair Databases Are Located (Gradual)
• Grow _Pair Database And Logs
• Grow SQL Tempdb And Logs
• Plan For WSS Tempdb Growth
• Set Affected Databases And Logs To Auto Growth
• Disable Full-text Search For Large Databases
24
