SharePoint-upgrade_15 Oct 2010

© 2010 WinWire Technologies

SharePoint 2010 Upgrade: Tips, Tricks and Pitfalls

Wired2Win Webinar Series

Vineet [email protected] Technologies Inc.

mailto:[email protected]


Agenda

● SharePoint 2010 Overview● Upgrade process

– Learn– Prepare– Test– Implement– Validate

● Best practices


SharePoint - Evolution


New SharePoint 2010 Features

There are lots of of new features that may be used to supersede controls you have implemented in your MOSS 2007 sites

● Server Ribbon● Publish process

– Auto spell-check– Unpublish items check

● One-Click page authoring● Content Organizer● Multilingual options● Digital media

– Silverlight viewer– Video streaming– Site Asset Library

● Cross-browser rich text editor with valid markup– No need for custom solution

● Metadata store upgrades– Enterprise taxonomies– Folksonomies– Rating– Tagging– Social feedback

● Dynamic Rollup Filtering● Site-based workflows


Preparing For Upgrade

• Read upgrade documentationLearn

• Use pre-upgrade checker command on existing environmentsPrepare

• Test upgrade on testing farm• Try proof of concept with current/upgraded

customizationsTest

• Upgrade to SharePoint 2007 SP2 (with October 2009 CU a plus) – if not already done

• Move to 64 bit hardware, operating system, and SQL

Implement

• Find issues early before releasing to usersValidate


Upgrade Cycle: Overview

Learn• 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


• 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


Hardware and System Software

● 64-bit all the way–Hardware and system software

● SharePoint Server 2010 is 64-bit only● SharePoint Server 2010 requires 64-bit Windows Server 2008 or 64-

bit Windows Server 2008 R2● SharePoint Server 2010 requires 64-bit SQL Server 2008 or 64-bit

SQL Server 2005

–Development● Visual Studio 2008 extensions for Windows SharePoint Services

(VSeWSS), version 1.3● Visual Studio 2010


Best Practices

● Update your servers to Service Pack 2 (SP2) of Microsoft Office SharePoint Server 2007 or later

● Ensure that the environment is fully functioning before you perform an upgrade

● Run the pre-upgrade checker to look for potential issues

● Perform a trial upgrade on a test farm first● Plan for capacity● Back up your environment● Optimize your environment before upgrade


MOSS 2007 Farm services

● Each SSP upgrades into:–A Search service app–A User Profiles service app–An Excel service app–An App Registry back-compat service app–A new managed metadata service app

● Web application associations are preserved–A proxy is created for each service app

● New databases are created as needed


Upgrade Cycle: Prepare

Plan upgrade strategy

Farm upgrade order

Order of operations

Downtime limits/mitigate

Rollback process

Hardware upgrades

Space requirements

Spring cleaning


Upgrade Planning

● 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


Farm/Customizations Surveys

● Gather information– Pre-upgrade checker (Updated in Oct 2009 CU)– Manual inspection process– Comparison process (WinDiff):

● New server with same version and patch level● Compare Web Server Extensions directory● Compare IIS directory● Compare GAC directory

● Determine impact– stsadm -o EnumAllWebs (Updated in Oct 2009 CU)

● Collect customizations– stsadm -o ExportIPFSAdminObjects


Environment Cleanup

● 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


Upgrade Cycle: Test

Build Test Farms• U

se real data (copies of entire databases):• T

o identify trouble areas

• To determine upgrade performance

• Use similar hardware if possible

Evaluate Techniques• U

pgrade process

• Downtime mitigation

• Troubleshooting/Validation

• Determine and test mitigations before upgrade

Find Issues Early


Upgrade Testing

● Upgrade Issues– Large lists– Modified databases– Customizations– Authentication

providers

● Recommendations– Full survey first– Test server side

customizations– Verify in both Visual

Upgrade modes– Consider preview

environments– Similar hardware– Use real datasets– Don’t ignore warnings


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


Create a new

SP 2010 farm

Install all

components

required in SP

2010

PreUpgradeCh

eck MOSS 2007 farm

Set MOSS 2007 DB

Read Only

BackUP

MOSS 2007 DB

Restore DB in

SQL Server

of SP2010

farm

PowerShell test

command

PowerShell

migration

commandMigrati

on finish

SharePoint 2010 Migration – Process


Example of Operations Scheduling

Example:– Planned 36 hours outage.– Up to 54 hours emergency outage if rollback is required.– Downtime mitigation processes such as read-only databases can be used to

reduce outage time.

Schedule Operation

Friday 2200hrs Start backups

Saturday 0000hrs Start upgrade of content farm/databases

Sunday 1200hrs

Upgrade must be effectively complete, or rollback of environment must begin

Monday 0600hrs

Environment must be completely working, either as original version or new version


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


Post-Upgrade Activities - I’ve finished upgrade, what’s next?

● Find and Fix Issues– Missing Templates– Deprecated Templates

● SSP Admin Site● Great Plains (STSPKPL)

– Missing Features– Deprecated Features

– PortalLayouts– Missing Assemblies

● Web parts (STSPKPL)

● Forms Based Authentication– Modify config files– Fix-up user identifiers

● User Experience– Unghosted pages– Non-reghostable

pages– Incompatible HTML

● Content Issues– Large/wide lists


Upgrade Failure Prevention

● Perform Farm Analysis– stsadm -o PreUpgradeCheck (Updated in Oct 2009 CU)– stsadm -o EnumAllWebs (Updated in Oct 2009 CU)

● Get Farm Healthy (Spring Cleaning)● Gather/Install Server Side Customizations

– stsadm -o ExportIPFSAdminObjects● Test Upgrade Beforehand● Perform Database Content Check (optional)

– Test-SPContentDatabase


Upgrade Failure Recovery

1. Determine cause of failure– Status Page & Upgrade 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


Questions

SharePoint-upgrade_15 Oct 2010

Technology