1eVision informacijski sustavi

Zvonimir Mavretić, Chief Technology Officer

Croatia SharePoint User Group

SharePoint 2010 Upgrade

Zagreb, 13.10.2011.

2

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

3eVision informacijski sustavi

Pre Upgrade

4

SharePoint 2010 Requirements

SharePoint 2007 SP2 Update (August CU recommended)64 bit operating system for application servers

•Windows Server 2008 or 2008 R264 bit SQL Server

•SQL 2005 SP3 CU3/2008 SP1 CU2/2008 R2For Development environments

•64-bit Vista SP1 and Windows 7Virtualization is supported and very common

5

Learning from PreUpgradeCheck

6

PreUpgradeCheck Failed Report (snippets)

7

SharePoint PreUpgradeCheck Report

Information & Configuration

• Content Sources & Start addresses

• Farm & Search Topology

• Servers• Upgrade Types• AAMs, Large Lists &

Libraries

ImportantIssues and

Dependencies• Site Definition

(referenced & missing)

• Installed Language Pack

• Features (referenced & missing)

• Custom List Views & Custom Field Types, Web.Config entries

8

Test-SPContentDatabase

9eVision informacijski sustavi

Upgrade

10

Insight on Upgrade

Binary Upgrade•In Place - New Timeout, Resume on failures•Database Attach - New Parallel, Progress

Indicator

Visual Upgrade•Separate process•Delegation by default

Binary Upgrade

Visual Upgrad

e

11

In-Place Upgrade

All-at-once upgrade•Must upgrade the whole farm at one time•No SP 2007 and SP2010 in same farm•Schedule downtime

Simplest approach, but *most risky*!•No going back

Resume Upgrade if problems occurRecommendations

•Run Test-SPContentDatabase from SP 2010 farm against databases•Do a full farm backup before you start!

12

1. In Place - Binary Approach to Upgrade

PreUpgradeCheck

on SP2007

farm

Test In Place

Upgrade on 2nd Farm

Fix issues

Mount and

Resume Dbs w/

Powershell

Fix Upgrade Errors

Visual Upgrad

e

Caution: Not recommended for most deployments…

13

Psconfig –cmd upgrade

14

Psconfig Upgrade Continued

15

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 with 2nd step visual upgrade

Use Test-SPContentDatabase (PowerShell cmdlet) to test database firstTo attach

•Mount-SPContentDatabase (PowerShell)•STSADM –o Addcontentdb operation

Parallel database upgrades are possible

16

Read-Only Databases

17

2. DB Attach - Binary Approach to Upgrade

PreUpgradeChec

k on SP2007

farm

Fix issues

Upgrade Services

Test-SPContentDatab

ases

Add solutions

/Fix issues

Database Attach Content Databas

es

Visual Upgrade

Recommended for most deployments…

18

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

19

Attaching Database to SP2010 Farm

20

Central Admin Upgrade Status

21

Post Binary Upgraded Site: Preview Visuals

22

Visual Upgrade Options

23

24eVision informacijski sustavi

Savjeti

25

Operations SchedulingBenchmark upgrade operations schedule

Note:•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

26

Common Upgrade Failure Issues & 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

27eVision informacijski sustavi

Upgrade Strategies

28

Windows PowerShell Upgrade Cmdlets

Test-SPContentDatabaseDiscover and Document issues 2007/2010Mount-SPContentDatabaseInitiate Content database B2B/V2V upgradeUpgrade-SPContentDatabaseResume Content database B2B/V2V upgradeUpgrade-SPEnterpriseSearchServiceApplicationSearch Service Application InstanceUpgrade-SPSingleSignOnDatabaseO12 SSO data to Secure Store database

29

Upgrade Testing

Upgrade Issues•Disk Full!!!•Modified databases•Customizations•Authentication providers•Poor dev practices

Recommendations•Test server side customizations & verify in both

Visual Upgrade modes•Consider preview environments•Similar hardware, Use real datasets•Don’t ignore warnings

30

Binary Approaches to Upgrade - Hybrid

Make a copy of the farm

Set databases Read-Only on Source

Upgrade Binaries

and Services with In Place

upgrade

Test-SPContentDatabas

es

Database Attach

Content Database

s in Parallel

Visual Upgrade

31

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

32

Visual Upgrade Caution

AAM redirection features is complex. Don’t use it if you don’t have to.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

33eVision informacijski sustavi

Q & A