© 2009 Quest Software, Inc. ALL RIGHTS RESERVED
Practical Guidance for Your SharePoint 2010 Upgrade: It’s Not Just Going from Point A to Point B
Joel Oleson
Sr. Product Architect
Quest Software
http://www.sharepointjoel.com
Contributions: Sean Livingston
2
SharePoint 2007 vs. 2010: Should I stay or Should I go?!!
Timeline Features
App Dev
Business
Connectivity
Social Networking
Business Risk
Averse
IT Not Ready
3
Upgrade Cycle: OverviewLearn
•Requirements/prerequisites
•Upgrade methods
•Downtime mitigation
•Common issues
Prepare
•Document environment
•Manage customizations
•Plan upgrade strategy
•Make items upgradable
Test
•Build test farms
•Use real data
•Evaluate techniques
•Find issues early
Implement
•Build/upgrade farms
•Deploy customizations
•Minimize downtime
•Monitor progress
Validate
•Upgrade event failures
•UI/UX issues
•Data issues
4
• 64 bit only
• Operating System
• SQL server
• In-Place
• Database Attach
• Content
• Profile
• Project
• WID to SQL Migration
• Missing dependencies
• UI changes
• Lack of space
• Forms Authentication Providers
• Read-only content databases
• Parallel upgrades:
• Multiple temporary farms
• Parallel database attach
• AAM redirection
Upgrade Cycle: Learn
Prerequisites
Upgrade methods
Common issues
Downtime mitigation
5
Upgrade Cycle: Test
Build Test Farms
•Use real data (copies of entire databases):
•To identify trouble areas
•To determine upgrade performance
•Use similar hardware if possible
Evaluate Techniques
•Upgrade process
•Downtime mitigation
•Troubleshooting/Validation
•Determine and test mitigations before upgrade
Find Issues Early
6
Upgrade Cycle: Implement
Build/upgrade farms
•Services farm
•Content farm
Minimize downtime
•Use read only with fallback environment
•Build for upgrade parallelism
Deploy customizations
•Use Solutions
whenever possible
Monitor progress
•Watch upgrade status indicators
•Ensure upgrade process
is on schedule
7
Upgrade Overview
• Drill Down on Binary Upgrade Methods– Windows PowerShell Upgrade
Cmdlets– Approaches to Upgrade
• Dev - Feature Upgrade• Visual Upgrade• Patch Management• Downtime Mitigation
Processes:– Parallel Upgrade Pipelines– Content DB Upgrade with AAM
Redirection
• Improved• Upgrade Status Reporting• Upgrade Logging• Read-only DB Support• Simplified Upgrade Methods
• Removed• Gradual Upgrade• Side By Side Installation
8
Upgrade Cycle: Validate
Upgrade event failures
Review logs to identify issue
Implement fixes
Restart/resume upgrade
Data issues
Orphaned items/database corruption
Hidden column data
Connectivity issues to data sources
UI/UX issues
Ghosting issues
UI Version issues
XHTML compliance issues
9
Drill down
10
Learning from PreUpgradeCheck
11
SharePoint PreUpgradeCheck Report
Information & Configuration
•Content Sources & Start addresses
•Farm & Search Topology
•Servers
•Upgrade Types
•AAMs, Large Lists & Libraries
Important
Issues and Dependencies
•Site Definition (referenced & missing)
•Installed Language Pack
•Features (referenced & missing)
•Custom List Views & Custom Field
Types, Web.Config entries
12
Test-SPContentDatabase
13
Attaching Database to SP2010 Farm
14
Insight on Upgrade
• Binary Upgrade– In Place (New No Timeout, Continue on failures)– Database Attach (New parallel Db upgrade, progress in CA & better logs)
• Visual Upgrade– Not required until next version– Separate process– You decide when & how!– Often delegated
Binary Upgrade
Visual Upgrade
15
Binary Upgraded Site: Preview Visuals – Sneak Peak Screenshot
16
17
In-Place Upgrade• All-at-once upgrade
– Must upgrade the whole farm at one time– Cannot intermingle SP 2007 and SP2010 in same farm– Schedule downtime
• Simplest approach, but *most risky*!– No going back
• Resume Upgrade if problems occur• Recommendations
– Run Test-SPContentDatabase from SP 2010 farm against databases
– Do a full farm backup before you start!
18
Database Attach Upgrade• Safer, Requires more planning (A good thing)• Upgrade is done on a separate 2010 farm
– Done database-by-database – Can be used as 2 step gradual visual upgrade
• Use Test-SPContentDatabase (PowerShell cmdlet) to test database first
• To attach– Upgrade-SPContentDatabase (PowerShell)– Addcontentdb operation (STSADM)
• Parallel database upgrades are possible
19
Visual Upgrade
• Stay in 2007 (default) or move to 2010 UI– 2010 ships 2007 Master pages and CSS– UI Preview capability
• Farm admin or site admin controlled– Web level setting
• Some items not 2007 UI compatible– My site host– PWA site collection– Report Server web parts
20
Unsupported Upgrade Methods
Unsupported Scenarios• Upgrade from earlier than WSS v3 SP2/MOSS 2007
SP2 (Requires SP2, but Oct CU or later is preferred)• Direct upgrade from WSS v2/SPS 2003 or earlier• Side by side installation• Gradual upgrade
• Third party tools like Quest Software Migration Manager will have support for Upgrade from 2003
21
Insights
22
2010 Upgrade PhilosophyWhat were we thinking• Detect issues early
– Provide O12 tools to admins– Report critical issues at start of upgrade
• Keep the administrator informed• No data loss
– Keep content and settings• Minimize downtime
– Downtime mitigation processes• Continue when possible• Be reentrant
– Upgrade should not be catch 22
23
Upgrade PerformanceWhy prediction is difficult
Database Shape Centric• # Site Collections• # Webs• # Lists• # Document Versions• Document Versions
Size• # Documents• # Links• Overall DB Size
Hardware Centric• SQL Disk I/O per
second• SQL Database to disk
layout• SQL Temp DB
optimizations• SQL CPU & Memory• WFE CPU & Memory• Network Bandwidth &
latency
24
Common Upgrade Failure Issues & Recovery
1. Determine cause of failure– Status Page & Upgrade Logs:– \Program Files\Common Files\Microsoft Shared\
Web Server Extensions\12\Logs• Error log• Full upgrade log
– Customizations Management Commands:• Test-SPContentDatabase• stsadm -o EnumAllWebs
2. Fix issue(s)– Install missing or updated customizations– Activate missing services; farm, web app settings
3. Resume upgrade– Farm upgrade command– Content database specific upgrade command– Service specific upgrade commands
25
Upgrade TestingWhat are you looking for in a test?• Upgrade Issues
– Long, Wide lists– Modified databases– Customizations– Authentication providers
• Recommendations– Test server side customizations– Verify in both Upgrade modes including visual– Consider read only preview– Similar hardware– Use real datasets– Don’t ignore warnings
26
Upgrade InternalsDetails• V2V upgrade DBs set to simple recovery• DB growth during upgrade:
– Versions and indexes; SQL logs– Shrink DBs after upgrade; not automatic
• SQL timeouts:– Removed command timeouts (query time)– Retained connection timeouts
• SetupPath fallback logic• Object locking during upgrade:
– Maintained in config DB– Automatic removal of stale locks (2 minutes)
27
Upgrade Strategies
28
Read-Only Content DatabasesReducing perceived downtime• Not just for upgrade or patching• Manually initiated process• Read-only locking:
– Content remains static– SQL controls read-only lock status– SharePoint promotes SQL lock to site lock– UI Trimming enforced by site lock
• Upgrade copy of database on different farm
29
Windows PowerShell Upgrade CmdletsTest-SPContentDatabase• Discover and Document issues 2007/2010
Upgrade-SPContentDatabase• Common Scenarios:
– Initiate/resume content database B2B upgrades– Resume failed content database V2V upgrades
Upgrade-SPEnterpriseSearchServiceApplication• Search Service Application Instance
Upgrade-SPSingleSignOnDatabase• O12 SSO data to Secure Store database
30
1. In Place - Binary Approach to Upgrade
PreUpgrade Check on
SP2007 farm
Test In Place
Upgrade on Farm
& Plan for
Disk/RAM
Fix issues
Resume with
Upgrade-
SPContentDataba
se
Fix Upgrade
ErrorsVisual Upgrade
Caution: Not recommended for most deployments…
31
2. DB Attach - Binary Approach to Upgrade
PreUpgradeChe
ck on SP2007
farm
Fix issuesUpgrade
Services
Test-
SPContentDatab
ases
Add solutions/Fix
issues
Database Attach
Content
Databases
Visual Upgrade
Recommended for most deployments…
32
Binary Approaches to Upgrade - Hybrid
Make a copy of
the farm
Detach all the
content
databases
except root site
Upgrade
Binaries and
Services with In
Place upgrade
Test-
SPContentDatab
ases
Database
Attach Content
Databases in
Parallel
Visual Upgrade
33
Downtime Mitigation Processes• Read-only databases• Parallel upgrade farms• Single farm, multiple upgrade sessions• Content database attach with AAM redirection
34
SSP to Service App• Each SSP upgrades into:
– A Search service app– A User Profiles service app– An Excel service app– An App Registry back-compat service app
• New Services can be activated/added
35
Visual Upgrade Capability• Stay in O12 UI (default) or move to O14 UI
– O14 ships O12 Master pages and CSS– UI Preview capability
• Farm admin or site admin controlled– Web level setting and OM
• Some items not O12 UI compatible:– My site host– PWA site collection– Report Server web parts
36
Visual Upgrade Caution• No Visual backward compatible UI for My Sites
– Database Attach into My Site Host– In place upgrade your My Site Host
• Other Services UI may be impacted– Project Web Access site collection– Reporting Server web parts
37
Depreciation• Performance Point – Included in SharePoint 2010
Enterprise • My Site Host Redesign – No visual upgrade for my sites • Side by Side Installation - Gradual Upgrade • SSP Admin UI – Any work you did on either the SSP
Admin Site Collection or the Central Admin site has changed.
• Admin task list and other CA lists • Document Discussions is deprecated. Not very common.• Deprecated Templates
– SSP Admin Site– Great Plains (STSPKPL (Plus Pack)
References: Deprecation of Features in SharePoint 2010
38
What about Custom Site Definitions?Most custom site definitions from v3 should continue to work unmodified while in v3 UI mode of Visual Upgrade. However depending on what is in that site definition, a person may still want to do more featurization or other definition refactoring, which is where the upgrade definition file comes in handy. As always, test the existing definition against an upgraded server in both UI modes
- Sean Livingston, Upgrade PM
39
Dev - Feature Upgrade Capability• Optional Capability• Declarative Feature Upgrade Activities:
– ApplyElementManifests– AddContentTypeField– MapFile
• Custom Code Feature Upgrade– CustomUpgradeAction Activity– SPFeatureReceiver.FeatureUpgrading– Assembly in GAC
40
Upgrade PlanningHow to manage a complex process – PMs Matter A LOT!• Customer Communications• Farm/Customizations Surveys• Upgrade/Customizations Testing• Environment Cleanup• Hardware Build-out• Customizations Deployment• Backups Before Upgrade• Operations Scheduling• Rollback/Restore Plan• Post-Upgrade Activities• Ongoing Support Calls
41
What can I do today to prepare?• Test!!!• Work towards 64-bit server environments• Upgrade to Service Pack 2 (SP2)• Review and identify your customisations• Cleanup as much as possible• Verify custom solutions work and deploy in 2010• Optimise your large lists• Optimise your content databases• Run PreUpgradeCheck that’s part of SP2
42
Announcing FREE!Quest Reports For SharePoint
43
http://www.quest.com/reportsforsharepoint
44
Quest Solutions for SharePoint Site Administrator for SharePoint
Understand, manage and secure your
SharePoint environment
Migration Manager for SharePoint
SharePoint to SharePoint migration
File Migrator for SharePoint
File shares to SharePoint migration
Recovery Manager for SharePoint
Granular SharePoint recovery for enterprise-level needs
Quest Web Parts
Enable rapid development
of SharePoint applications
Public Folder Migrator for SharePoint
Exchange Public Folders to SharePoint migration
Notes Migrator for SharePoint
Notes application content to SharePoint migration
Quest SQL Server Solutions
Maximize SQL Server performance while simplifying tasks and
providing visibility and control
45
Technology Responsibilities
45
Toughest Challenges
1. User Provisioning/de-provisioning
2. Delegation of Admin Rights
3. Compliance Reporting
4. Disaster Recovery
Active Directory44%
DNS26%
MIIS/ILM16%
Ex-chang
e15%
Multiple Technology Respon-sibilities
Technology Used / Deployed
• 99% MS Server OS
• 90% Management Frameworks
• 55% - MOM
• 27% - HP OpenView
• 21% - IBM Tivoli
• 87% Exchange
• 74% SharePointSource: DEC 2008 Attendee Survey Whitepaper
46
Thank You!
47
Q&A
48
Additional Resources• Slides: Preparing for Upgrade to SharePoint 2010 Today• Article: Preparing for SharePoint 2010 Upgrade Today • Upgrade Resources: http://www.SharePointJoel.com!
SharePoint 2010 Upgrade Resource Centers • Upgrade and migration resource center for SharePoint Fo
undation 2010 - TechNet
• Upgrade and migration resource center for SharePoint Server 2010 – TechNet
• SharePoint 2010 Upgrade Resource Center – MSDN • SharePointUpgrade.com - Community driven wiki based
SharePoint 2010 Upgrade resources