Upgrading to SharePoint 2013
Sam Hassani
• Who am I?
–
–
–
–
–

Sam Hassani
Principal Consultant @ BrightStarr
Microsoft Certified Master: SharePoint
SharePoint 20...
Agenda
•
•
•
•
•
•
•

Design Goals
Upgrade Improvements
Advanced Upgrade Scenarios
Customizations and Upgrades
Planning Fa...
Design Goals
• Safer upgrades
– Removal of in-place upgrades
– Adding site collection health checks
– Adding evaluation si...
Deferred Site Collection Upgrade
• Eliminate big bang upgrades
–
–

Upgrade database now, upgrade site collections later
K...
Site Collection Health Checks
• Rule based health checks to look for common known issues
–
–

Ownership can be delegated t...
Upgrade Evaluation Site Collections
•

An upgraded copy of the original site collection
–

•

Not intended for long term u...
Timer Job:
Create Evaluation Sites

4
SPSite

“/sites/foo”

SPSite

“/sites/foo”

5

SPSite
Cloning

3

“/sites/foo-eval”
...
Site Collection Upgrade Throttling
• Prevents overload from self-service site collection upgrade
• Built-in throttles work...
Self-Service Site Collection
Upgrades
•

Site collection admin chooses when to upgrade
– Self service user interface to st...
My Site Upgrades
•
•
•

Experience changes depend on My Site Host Upgrade State
My Site Host should always upgrade before ...
My Site Upgrades
Start: All existing social sites in 14 mode
1. X visits My Site Host, sees 14 experience
2. X visits own ...
Supported Databases
•

Content databases

•
•
•
•
•
•
•

Search admin database
Profile database
Social database
Managed Me...
Service Application Upgrade
1. Backup Service Application databases from source farm
2. Create each service application an...
Service Application Upgrade
Example
$applicationPool = Get-SPServiceApplicationPool -Identity "SharePoint Service Applicat...
Service Application Upgrade
Example 2
$applicationPool = Get-SPServiceApplicationPool -Identity "SharePoint Service Applic...
Federated Services Compatibility
Cross Versions
Site Collection Modes
14
Mode
Site
Page

15
Mode
Site
Page

In-process request routing

/_layouts/

Page

Page
Code

SP201...
Feature Fallback Behaviour

15 Mode Lookups

15 Mode Features List

SP2013 feature replacing
SP2010 feature

New SP2013 on...
Unsupported In 2010 Mode
• All new SP2013 specific features
– Upgrade SPSite to 15 mode first

• 2010 Web Analytics
– Exis...
Build SharePoint
2013 Farm
Upgrade Site
Collections

Deploy Solutions

Validate
Environment

Copy and Restore
Databases

C...
Environment clean-up
• Gather data on existing farms (i.e. farm surveys)
–
–
–

Collect all settings within the farm
Get r...
Environment clean-up cont’d.
• Content preparation
–
–
–

Delete excess columns from wide lists
Remove extraneous document...
Information Gathering Methods
• STSADM -o PreUpgradeCheck no longer exists
– STSADM deprecated
• WinDiff
• STSADM –o EnumA...
Test-SPContentDatabase
• Finds issues with content databases when compared to a
specific web application
– Missing Customi...
Testing Upgrade
• Testing environment should be as similar as possible to real
environment
• Use real data
• Run multiple ...
Upgrade Performance
Database Shape Centric

Hardware Centric

•
•
•
•
•
•
•
•

•
•
•
•
•
•

# Site Collections
# Webs
# Li...
Formulate Upgrade Plan
• Determine upgrade strategy
–
–

Upgrade preparation, testing, implementation, validation
Farm Con...
When it all goes wrong…
• Upgrade Status Page in Central Administration
• Upgrade Logs
–
–
–

ULS Logging
Correlation Ids
...
Lessons Learned
•

•

Ensure that the environment is fully functioning before you begin
upgrade
Cleanup and Preparation
–
...
Thanks to our
Sponsors
Upgrading to SharePoint 2013 - SharePoint Saturday UK 2013
Upgrading to SharePoint 2013 - SharePoint Saturday UK 2013
Upgrading to SharePoint 2013 - SharePoint Saturday UK 2013
Upgrading to SharePoint 2013 - SharePoint Saturday UK 2013
Upgrading to SharePoint 2013 - SharePoint Saturday UK 2013
Upgrading to SharePoint 2013 - SharePoint Saturday UK 2013
Upgrading to SharePoint 2013 - SharePoint Saturday UK 2013
Upgrading to SharePoint 2013 - SharePoint Saturday UK 2013
Upgrading to SharePoint 2013 - SharePoint Saturday UK 2013
Upgrading to SharePoint 2013 - SharePoint Saturday UK 2013
Upgrading to SharePoint 2013 - SharePoint Saturday UK 2013
Upgrading to SharePoint 2013 - SharePoint Saturday UK 2013
Upcoming SlideShare
Loading in …5
×

Upgrading to SharePoint 2013 - SharePoint Saturday UK 2013

967 views
795 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
967
On SlideShare
0
From Embeds
0
Number of Embeds
115
Actions
Shares
0
Downloads
21
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Upgrading to SharePoint 2013 - SharePoint Saturday UK 2013

  1. 1. Upgrading to SharePoint 2013 Sam Hassani
  2. 2. • Who am I? – – – – – Sam Hassani Principal Consultant @ BrightStarr Microsoft Certified Master: SharePoint SharePoint 2013 Beta Engineer PFE SharePoint 2013 Ignite Instructor – sam.hassani@brightstarr.com – @samhassa – www.samhassani.com
  3. 3. Agenda • • • • • • • Design Goals Upgrade Improvements Advanced Upgrade Scenarios Customizations and Upgrades Planning Farm Upgrades Troubleshooting Upgrades Lessons Learned
  4. 4. Design Goals • Safer upgrades – Removal of in-place upgrades – Adding site collection health checks – Adding evaluation sites to allow preview of what upgrade will do • Reduced outage duration – Separating 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 people – Let 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
  5. 5. Deferred Site Collection Upgrade • Eliminate big bang upgrades – – Upgrade database now, upgrade site collections later Keep existing customizations, updated ones can wait • Provide self-service site collection upgrade capability – – Site collection admins can easily do the upgrade Admins can still do upgrades or prevent users from doing them • Upgrade-SPSite • Move forward at a manageable pace – – Initially let users stay with 2010 experience Gradually move users over to 2013 experience
  6. 6. Site Collection Health Checks • Rule based health checks to look for common known issues – – Ownership can be delegated to Site Collection Administrators Farm Admins can use Test-SPSite and Repair-SPSite • Runs automatically before Site Collection upgrade – Prevents upgrade if blocking issues detected • Can be run without doing upgrade
  7. 7. Upgrade Evaluation Site Collections • An upgraded copy of the original site collection – • Not intended for long term use – – – • • • More than visual upgrade Read/Write Pre-determined URLs Expiry (farm admin controlled) Can be turned on/off Maximum size can be set Sends email notification when copy and upgrade is completed – – Requester and all site collection administrators Email is optional if request occurs via PowerShell
  8. 8. Timer Job: Create Evaluation Sites 4 SPSite “/sites/foo” SPSite “/sites/foo” 5 SPSite Cloning 3 “/sites/foo-eval” AllSites Filtered Copy Of AllSites AllSites AllWebs Filtered Copy Of AllWebs AllWebs AllDocs Filtered Copy Of AllDocs AllDocs … Filtered Copy Of … … Snapshot Database Content Database 2 1 R/O Content Database 6 4 Evaluation Clone SPSite Site Map / /sites/foo /sites/foo-eval Sites Configuration Database
  9. 9. Site Collection Upgrade Throttling • Prevents overload from self-service site collection upgrade • Built-in throttles work together: – Application pool level throttle – Content Database level throttle – Content throttle • If an upgrade is not possible due to throttling it is queued – Queued upgrades are processed by the timer service by upgrade timer job
  10. 10. Self-Service Site Collection Upgrades • Site collection admin chooses when to upgrade – Self service user interface to start and review upgrade • Health checks help ensure site is ready for upgrade – Health checks run in repair mode during version upgrade • Farm admin chooses if upgrade is available or not – Can 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
  11. 11. My Site Upgrades • • • Experience changes depend on My Site Host Upgrade State My Site Host should always upgrade before Personal Sites Only My Site Host Site collection admin can upgrade My Site Host
  12. 12. My Site Upgrades Start: All existing social sites in 14 mode 1. X visits My Site Host, sees 14 experience 2. X visits own Personal Site, sees 14 experience 3. Y visits My Site Host, sees 14 experience Gets new 14 mode Personal Site 4. 5. Y X Z My Site Host is upgraded to 15 mode by farm admin X visits My Site Host, sees 15 experience My Site Host Personal Site gets queued for upgrade 6. 7. 8. 9. 14 Mode 15 X visits own Personal Site before upgrade, sees 14 experience X Personal Site upgrades through timer job X visits own Personal Site after upgrade, sees 15 experience 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 X Personal Site 14 Mode 15 Q User Y Personal Site 14 Mode 15 Q User Z Personal Site 15 Mode
  13. 13. Supported Databases • Content databases • • • • • • • Search admin database Profile database Social database Managed Metadata database Subscription Settings database PerformancePoint database Secure Store database – • Note: Passphrase required to retain passwords in store Business Data Connectivity Database
  14. 14. Service Application Upgrade 1. Backup Service Application databases from source farm 2. Create each service application and proxy – – If applicable, upgrade service database during service application creation Pay special attention to differences in some services • Most service upgrade processes are the same, some are different 3. Start service instances only after service is created with upgraded databases
  15. 15. Service Application Upgrade Example $applicationPool = Get-SPServiceApplicationPool -Identity "SharePoint Service Application" # Create Business Data Catalog service and proxy $sa = New-SPBusinessDataCatalogServiceApplication -Name "Business Data Catalog Service Application" -ApplicationPool $applicationPool -DatabaseName “BDC_Upgrade_DB" if ($sa) { New-SPBusinessDataCatalogServiceApplicationProxy -ServiceApplication $sa -Name "Business Data Catalog Service Application Proxy" -DefaultProxyGroup #Start Business Data Catalog service Get-SPServiceInstance | Where-Object {$_.TypeName -Eq "Business Data Connectivity Service"} | Start-SPServiceInstance }
  16. 16. Service Application Upgrade Example 2 $applicationPool = Get-SPServiceApplicationPool -Identity "SharePoint Service Application" # Restore Enterprise service and create proxy $searchInstance = Get-SPEnterpriseSearchServiceInstance -local $sa = Restore-SPEnterpriseSearchServiceApplication -Name "Search Service Application" ApplicationPool $applicationPool -AdminSearchServiceInstance $searchInstance -DatabaseName “SearchAdmin_Upgrade_DB" if ($sa) { New-SPEnterpriseSearchServiceApplicationProxy -ServiceApplication $sa -Name “Search Service Application Proxy“ -Uri $sa.Uri.AbsoluteURI #Start Enterprise Search service Get-SPServiceInstance | Where-Object {$_.TypeName -Eq "Search Server Service"} | StartSPServiceInstance }
  17. 17. Federated Services Compatibility Cross Versions
  18. 18. Site Collection Modes 14 Mode Site Page 15 Mode Site Page In-process request routing /_layouts/ Page Page Code SP2013 App Process Space WSE/14/Templates/ Layouts Code WSE/15/Templates/ Layouts 14 Assembly Redirect Policy 15 Assembly SP2013 Config Databas e WSE/14/Templates SPSite SPWeb /_layouts/1 5/ SPSite SP2013 Content Database SPWeb WSE/15/Templates
  19. 19. Feature Fallback Behaviour 15 Mode Lookups 15 Mode Features List SP2013 feature replacing SP2010 feature New SP2013 only feature “Sunset” feature Visible=false 14 Mode Lookups 14 Mode Features List SP2010 feature replaced by SP2013 feature Non-replaced SP2010 only feature (e.g. 3rd party) SP2010 feature removed in SP2013
  20. 20. Unsupported In 2010 Mode • All new SP2013 specific features – Upgrade SPSite to 15 mode first • 2010 Web Analytics – Existing features must be removed – New web analytics features supported only in 15 mode • 2010 Office Web Applications – Replaced with SP2013 Office Web Applications for both 14 and 15 mode – PowerPoint Broadcast sites must be removed • No replacement available, use Lync instead
  21. 21. Build SharePoint 2013 Farm Upgrade Site Collections Deploy Solutions Validate Environment Copy and Restore Databases Create and Upgrade Service Applications Mount Content Databases Create Web Applications
  22. 22. Environment clean-up • Gather data on existing farms (i.e. farm surveys) – – – Collect all settings within the farm Get report on farm state including services, databases, and sites Collect all customizations with installation/configuration documents • Site Management – – – – Delete unused or underused sites Consider moving site collections into separate databases – 9000 ->5000 default limit Finish Visual Upgrades in SharePoint 2010 Removed unused templates, features and Web Parts
  23. 23. Environment clean-up cont’d. • Content preparation – – – Delete excess columns from wide lists Remove extraneous document versions Check Databases for duplicate or orphaned site collections • Migrate classic-mode web applications to claims-based authentication
  24. 24. Information Gathering Methods • STSADM -o PreUpgradeCheck no longer exists – STSADM deprecated • WinDiff • STSADM –o EnumAllWebs -includefeatures -includewebparts • Test-SPContentDatabase – Both 2010 and SP2013 versions
  25. 25. Test-SPContentDatabase • Finds issues with content databases when compared to a specific web application – Missing Customizations – Orphans • Largely unchanged in SP2013 • New parameters: – ShowRowCounts – ShowLocation – ExtendedCheck
  26. 26. Testing Upgrade • Testing environment should be as similar as possible to real environment • Use real data • Run multiple tests • Do not ignore errors or warnings • Test the upgraded environment, not just the upgrade process
  27. 27. Upgrade Performance Database Shape Centric Hardware Centric • • • • • • • • • • • • • • # Site Collections # Webs # Lists # Document Versions Document Versions Size # Documents # Links Overall DB Size SQL Disk I/O per second SQL Database to disk layout SQL Temp DB optimizations SQL CPU & Memory WFE CPU & Memory Network Bandwidth & latency Note: Each new build’s upgrade could be impacted by newly added upgrade actions or database content changes
  28. 28. Formulate Upgrade Plan • Determine upgrade strategy – – Upgrade preparation, testing, implementation, validation Farm Configuration, Service Applications, Content and Customizations • Plan business continuity – Outage length planning and mitigation methods • Build schedule • Plan communications
  29. 29. When it all goes wrong… • Upgrade Status Page in Central Administration • Upgrade Logs – – – ULS Logging Correlation Ids Categorization of Operations • ULS Logs • Site collection upgrade logs • Use Upgrade-SPContentDatabase to resume failed upgrade
  30. 30. Lessons Learned • • Ensure that the environment is fully functioning before you begin upgrade Cleanup and Preparation – • Treat pre-production testing like production – – • Use real data on real hardware, test everything for best results Production upgrade operations is not the time to learn anything new Formulate and validate an Upgrade Plan – • Cleanup soonest or pay upgrade tax repeatedly Determine approach to take Upgrade is a science – – Test carefully, not skipping errors or warnings Make operations procedural and repeatable
  31. 31. Thanks to our Sponsors

×