This slide is a copy of the talk given by Shereen at SharePoint Saturday LA on upgrading a SharePoint 2010 environment to SharePoint 2013 including backup of service applications and content databases, testing, installation and upgrade.
2. Co-Founder of Dynamic Owl Consulting
Microsoft Certified Professional
Organizer of Vancouver SharePoint Developers Group
Blog: sharepointdeveloperhq.com | blog.qumsieh.ca
Contributing Author
SharePoint Trainer & Speaker
Introduction: Shereen Qumsieh
2
Headshot
3. Dynamic Owl
3
• SharePoint consulting services
• Custom development & infrastructure
• Critical Path certified training company
• Business focused
- Strategy & Roadmap
- Governance
- Change Management
- Requirements Elicitation
- Intranets and Digital Workplaces
4. Today’s Agenda
4
• What’s new with upgrading to SharePoint 2013
• Overview of the upgrade process
• Lessons learned and best practices for upgrade
• Demo: Upgrading from SharePoint 2010 to SharePoint 2013
5. What’s new with upgrading to
SharePoint 2013
What do we need to know before planning our upgrade?
6. Options for upgrade in previous versions
6
SharePoint 2003 to 2007
• Database attach, In-place upgrade, Gradual upgrade1
SharePoint 2007 to 2010
• Database attach, In-place upgrade2
SharePoint 2010 to 2013
• Database attach3
7. What’s been improved
7
• Deferred site collection upgrade
• Site collection health checker
• Upgrade evaluation site collections
• Notifications for life-cycle events
• Throttles for site collection upgrade
• SharePoint compatibility modes
• Upgrade logging
8. Deferred Site Collection Upgrade
8
• All upgraded site collections initialized in 2010
UI mode
• Site collection administrators can now upgrade
their sites at their leisure
• No longer requires that farm administrators
manage this task
9. Site collection health checker
9
• Health checks help prepare for an upgrade
• Looks for common issues and displays a report
of findings
• Blocks upgrade if issues are detected
• Available for site collection administrators
10. Upgrade evaluation site collections
10
• Allows you to preview an existing site in
SharePoint 2013
• SharePoint creates a copy of the site collection
• Takes advantage of SQL Snapshot capability if present
- Causes no read-only outage as source is snapshot
- Available in SQL Enterprise and SQL Developer editions
• Otherwise uses site collection backup process
- Causes read-only outage during copy
• Changes made to evaluation site do not affect
original
• Set to expire and delete automatically
11. Notifications for life-cycle events
11
• Status bar notification alerts that upgrade is
available
• Status bar notifies if site is in read-only mode
12. Throttles for site collection upgrade
12
• Ensures that upgrades do not affect your farm
• Even if 100 administrators design to upgrade
at the same time, not all are run at the same
time
• Built in throttle defaults
• Web app: 5
• Content database: 10
• Content of a site: < 10MB and has < 10 sub webs
13. SharePoint compatibility modes
13
• SharePoint 2013 can support 14 and 15
modes
• Your 2010 solutions will continue to work in
2013
• Also known as compatibility levels
• Identify customizations in your environment
• Is the customization still valuable?
• Keep the customizations, don't upgrade the sites
• Replace or redo the customizations
• Discard the customizations
14. Upgrade logging
14
• Use the Upgrade Status page in Central
Administration
• Review the log files to look for errors or
warnings
• Changed to ULS format
• Can be imported into Excel
• Includes Correlation ID
15. Overview of the upgrade
process
I’m ready to upgrade, now what?
16. What are the steps?
16
• Create SharePoint 2013 farm
• Backup SQL databases in SharePoint 2010
farm and copy to new farm
• Restore SharePoint 2010 databases in
SharePoint 2013 farm
• Upgrade services applications to update their
table schemas for SharePoint 2013
• Mount content databases to existing web
applications
• Upgrade site collections
17. Database-attach support
17
• Supported
• Content databases
• Business Data Connectivity
• Managed Metadata
• PerformancePoint
• Secure Store
• User Profile (Profile and Social)
• Search administration
• Not supported
• Configuration database
• Search index database
• Sync database
18. Authentication support for upgrade
18
• SharePoint 2013 does not support classic
mode via UI, must be done via PowerShell
• Recommended that you upgrade to Claims
prior to migration to 2013
• Test-SPContentDatabase will detect issues
with authentication
19. Test-SPContentDatabase
19
• Finds issues between content DB and web
application
• Can test a database not connected to the farm
• Can test a database already connected to the farm
• Lists out issues including orphans
• Missing referenced server side customizations
• Missing Features
• Missing Templates/Site Definitions
• Missing Web Parts
20. Mount-SPContentDatabase
20
• Initiates Content Database upgrade
• Ensure you mount the content db that contains
the root site collection
• Runs internal consistency/orphans check
• Runs web application compatibility checks
• Web parts
• Features
• Site Definitions
• Event handlers
• Authentication/security migration references
22. Best practices for upgrade
22
• Build out a test farm to run a trial upgrade
• Take stock of all customizations and determine
whether or not they are required
• Remove any existing products or features you
no longer require
• Set your database to read-only in production
farm
• Ensure solutions are installed in 14 mode
27. Atera Prime K2
Axceler KnowledgeLake
CBT Clips KwizCom
Dell QuickStart
Hershey Technologies Virtualworks
Platinum
& Gold
Sponsors
Silver
Sponsors
Notas del editor
THIS SHOULD BE YOUR SECOND TO LAST SLIDE – Encourage everyone to attend and remind them that the Daily Pint is just a few blocks up Pico from SMC (North East)
THIS SHOULD BE YOUR LAST SLIDE – Please ensure to leave this on as people are walking out and you’re wrapping things up. Thanks so much!