SharePoint 2013 Upgrade OverviewSean LivingstonSenior Program Manager

SPC211

AgendaDesign Goals for 2013 UpgradesSite Collection UpgradesDeferring Site Collection UpgradeSite Collection Health ChecksEvaluation Site CollectionsSelf-Service Site Collection UpgradesQueuing Site Collection upgradesDemos

Upgrading the Social ExperienceMy Site Host and Personal Site upgrades

Upgrades with SQL

SnapshotsSnapshot Database Upgrades

System NotificationsSystem Status BarUpgrade email templates

Miscellaneous Upgrade ItemsUpgrade Log ImprovementsMaintenance Log

Farm Upgrade OverviewPlanningPreparingExecutingFinishing

Design Goals for 2013 UpgradesSafer upgradesRemoval of in-place version to version upgrades (Note: Build to build in-place upgrades still work fine)Adding site collection health checksAdding evaluation sites to allow preview of what upgrade will do

Reduced outage durationSeparating database upgrade from site collection upgrade (*saves ~2/3 upgrade time)Mitigate more outages with read only time providing air cover for operations

Power to the peopleLet site collection admins control their own destiny (*within farm admin controlled limits)Tell users what’s happening using upgrade email messages and system status bar

Site Collection Upgrades

Deferred Site Collection UpgradeEliminate big bang upgradesUpgrade database now, upgrade site collections laterKeep existing customizations, updated ones can wait

Move forward at a manageable paceInitially let users stay with 2010 experience:• Stay with the familiar• Keep using existing customizations

Gradually move users over to 2013 experience:• As training occurs (e.g. incrementally for each team)• As users decide to adopt new experience/features• As new version compatible customizations are available

Provide self-service site collection upgrade capabilitySite collection admins can easily do the upgradeAdmins can still do upgrades or prevent users from doing them

Site Collection Health ChecksRules can detect and in some cases repair issuesRules can exist for use in 14 and/or 15 modesSame or different rules may apply

Runs automatically in repair mode during version upgradeErrors block site collection version upgrade

Can be run without doing upgradeGive advanced notice of potential future issues

Evaluation Site CollectionsCopy of existing site collectionCopy not intended for long term use; Evaluation site collection cannot become permanentVersion upgraded automatically as defaultCopy made using snapshot or site collection backup/restoreCan only have one evaluation site collection for a given source site collection

Self-service creation only for small site collectionsMaximum size configurable by farm admin controlled web application level settingsLarge ones need farm admin to do create the evaluation site collection

Farm admin can copy any site collection as an evaluation site collectionPowerShell command to Request-SPUpgradeEvaluationSite queues creation

Evaluation site collections expireExpiration date tracked on each evaluation site collectionExpiration date based on creation date and farm admin controlled expiry delay

Self-Service Site Collection Upgrades

Site collection admin chooses when to upgradeSelf service user interface to start and review upgrade

Health checks help ensure site is ready for upgradeHealth checks run in repair mode during version upgrade

Farm admin chooses if upgrade is available or notCan block or allow all or specific site collection upgrades at the following levels:• Web application using SPWebApplication.CompatibilityRange• Site Collection using SPSite.AllowSelfServiceUpgrade

Can set parameters on max upgrade limits and upgrade parallelism

Queuing Site Collection UpgradesThrottles limit the number of parallel upgradesIn web application worker process:• Maximum in process site collection upgrade limits• IIS Process parallel site collection upgrade limit

In any process:• Content database parallel site collection upgrade limit

Upgrade requests are always queuedWeb application worker process overload will wait for process and database space• Note: This will never upgrade oversize site collections in the web application process

Timer jobs pick up queued items in content database jobs• Note: This includes queued oversize site collections

An unexpected failed site collection upgrades will resume automaticallyCorrectly failed upgrades will not resume as intervention is required

Status of all queued upgrades are tracked within the queueEventually every site collection will have a single queue entry once it gets upgraded

Demo

Performing Self-Service Site Collection Upgrades

Upgrading The Social Experience

My Site Host and Personal Site upgradesExperience changes depend on My Site Host Upgrade StateVisiting 14 mode My Site Host shows 14 social experienceVisiting 15 mode My Site Host shows 15 social experience and queues Personal Site upgradeVisiting 14 mode Personal Site shows 14 experience regardless of My Site Host upgrade statusVisiting 15 mode Personal Site shows 15 experience correctly only if My Site Host is upgraded to 15 mode

My Site Host should always upgrade before Personal SitesPrevents unexpected states in social features

Periodic retries upgrade on upgrade failuresIf a Personal Site upgrade fails, the My Site Host will try to upgrade Personal Site periodically on future visitsUpgrade timer job will retry queued upgrade if failure was unexpected

Only My Site Host Site collection admin can upgrade My Site HostPrevents users from moving environment to 15 mode until owners of social experience decide to do so

Social Upgrade AnimationStart: All existing social sites in 14 mode1. X visits My Site Host, sees 14

experience2. X visits own Personal Site, sees 14

experience3. Y visits My Site Host, sees 14

experienceGets new 14 mode Personal Site

4. My Site Host is upgraded to 15 mode by farm admin

5. X visits My Site Host, sees 15 experience

Personal Site gets queued for upgrade

6. X visits own Personal Site before upgrade, sees 14 experience

7. X Personal Site upgrades through timer job

8. X visits own Personal Site after upgrade, sees 15 experience

9. Y visits My Site Host, sees 15 experience

Personal Site gets queued for upgrade and later upgrades

10. Z visits My Site Host, sees 15 experience

Gets new 15 mode Personal Site

11. Z visits own Personal Site, sees 15 experience

User XPersonal Site

14 Mode15 Mode

User YPersonal Site

14 Mode15 Mode

User ZPersonal Site

15 Mode

My Site Host

14 Mode15 Mode

X Z

Q Q

Y

Upgrade with SQL Snapshots

About SQL SnapshotsCopy page on writeUses little space to begin withGrows over time up to 100% of source from when was snapshot taken

Slight performance hit per snapshotAdding more snapshots for a database means more performance hit (more copies to maintain)

Snapshot cannot be taken on a mirror PrimarySnapshot can be taken on the mirror Secondary however

Snapshots can be used with SQL 2012 AlwaysOn featureSnapshot can be taken on Primary and Secondary if not recovering

File system for Snapshots must not be Fat32 or RAWSnapshots cannot be used with FileStream file groups

Snapshot Database UpgradeIntended for Build to Build upgradesDoes not work for Version to Version upgrade

Allow upgrade and reverting of entire database upgradeUsers see read only outage during upgrade

Recommend omitting site collections during upgradePrevents possible site collection upgrade errors from reverting whole database upgrade

Command line operation onlyUpgrade-SPContentDatabase -UseSnapshot -NoB2BChild

Snapshot Use In Database Upgrade1. User works within site collection in

source database2. Upgrade-SPContentDatabase -

UseSnapshot command is invoked, database snapshot created

3. New snapshot listed for content database

4. User temporarily works with read only mode site collection in snapshot database

5. Source content database is upgraded6. User works within site collection in

upgraded source database7. Snapshot is cleaned up

SharePoint

PowerShell Process

PerformingUpgrade

Web Applicatio

nProcess

R/O

Con

ten

t D

ata

base

Site

Site

Site

Site

Snapshot Database

Con

ten

t D

ata

base

Site

Site

Site

Site

Con

fig

ura

tion

Data

base

Config Object:DatabaseSnapshot

Config Object:Content

Database

2

5

3

641

7

Limits To Using Snapshots With UpgradeSnapshots cannot be used with mirroringSnapshot enabled content database upgrade does not work with mirroringLimitation of SQL Server snapshot feature - cannot create snapshot on primary of mirror

Snapshots cannot be used with SQL RBS FileStream providerLimitation of SQL Server snapshot feature - cannot snapshot database with FileStream stores

System Notifications

System Status BarDisplays system level information to end users:Upgrade in progressUpcoming maintenance window plannedMaintenance in progress

Site read only (i.e. Creating evaluation/copying/moving/backing up)Database read only

Site collection read only at Farm admin requestSite collection read only at Site collection admin requestSite collection is for evaluation purposes and will expire

Displays important system level details to administrators:Site upgrade available

Optional notify later link to hide message for a while

Notification bar at top of browserShows two messages at most due to impact on screen real estate

Tied to core rendering control Cannot easily be customized outHelps ensure this shows up even on heavily customized sites

Custom messages not supportedOptional link to more information can point to custom locations

Can be closed for page viewingShows up on next full page refresh or cross page navigation

Can be hidden per site collectionWill be all or nothing change, cannot show any messages if hiddenNote: Only intended for use in special Internet facing scenarios

Upgrade Email Templates

Optional email sent out for various upgrade events• Site collection upgrade available• Evaluation site collection requested• Evaluation site collection created (with or without upgrade)• Evaluation site collection expiring soon• Evaluation site collection expired • Site collection upgrade succeeded• Site collection upgrade failed

Based on templates that can be modified with featuresTemplates can be adjusted per language/region

Email sending is controllableSPWebApplication.SendSiteUpgradeEmails

Miscellaneous Upgrade Improvements

Upgrade Log ImprovementsULS LoggingTSV format with headers, easily imported into ExcelSeparate Site Collection level upgrade logs (SiteUpgrade_DateTime.log)

Correlation IdsHelps track specific upgrade sessions into ULSAlso helpful tracking unique sessions from merged parallel upgrade logs

Error CodesCan help determine error cause/location/fix in debugging (Binging for answers)Some progress at RTM, more codes will follow

Categorization of OperationsBetter detail to track when entering/exiting sequences and actionsPlanned for future update

Maintenance LogGallery added during any upgradeOnly added if it doesn’t existWill add during both version to version and build to build upgrades

Contains site collection upgrade logsOnly contains local site collection’s reduced logging level upgrade logFull site collection and database logs still on file system for farm admin access

Logging level is separate from file system upgrade logsLess detail than file system logs, not configurable

Farm Upgrade Overview

Planning Farm Upgrades

Learn about upgrade (how it works, what to plan for)Documentation/postersTrainingTry it out on a test environment

Gather data on existing farms (i.e. farm surveys)Collect all settings within the farmGet report on farm state including services, databases, and sitesCollect all customizations with installation/configuration documents

Plan business continuityOutage length planning and mitigation methods

1. Remove orphaned items• PowerPoint Broadcast sites• Web analytics• Customizations you can’t move forward (e.g. incompatible with 2013)

2. Build-out new 2013 farm(s)• If using federated services on different farms, target the services farm

first• If possible leave old farms running while upgrading to new ones (for

outage reduction)• Set farm CompatibilityRange as appropriate• Install customizations onto new farm• Ensure you install customizations for both 14 and 15 mode as appropriate

Preparing Farm Upgrades

1. Backup everything2. Upgrade services first

• Search Administration database• Profile, Social, and Sync databases• Managed Metadata/Taxonomy database• Secure Store database• Remember to have Secure Store passphrase or you will lose all existing passwords

• Project Server databases• Remember to merge the four 2010 Project databases before attempting upgrade

3. Upgrade content databases• Site collection upgrade automatically deferred

4. Upgrade site collections at your leisure

Executing Farm Upgrades

• Confirm successful upgrade state• Verify services and content rendering• Fix issues if necessary

• Enable/disable self-service upgrades as required• Default allows upgrades and creation of 2010 site collections• Change web application CompatibilityRange• Old, OldVersions, or 14 will prevent 2013 site collection creation except for farm

administrators• Old, NewVersion, or 15 will prevent 2010 site collection creation except for farm

administrators, but will allow upgrade of 2010 site collections by site collection admins

• All, AllVersions, or “14,15” will allow both 2010 and 2013 site collection creation and upgrade by site collection admins

• Re-index existing content

Finishing Up Farm Upgrades

Evaluate this session now on MySPC using your laptop or mobile device: http://myspc.sharepointconference.com

MySPC

© 2012 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.