Upgrade and migration within the SharePoint environment has always been a specific challenge to all fields inside a company. Upgrade or migration will always give you the possibility to remove and eliminate old waste or fault design. Further the chances to customize your SharePoint environment conform to actual company structures. This lecture will show the fundamental procedure during migration, the possibilities of using internal means and the need of 3rd party tools.
Based on praxis examples we will respond to problems, offer solutions to migration and consolidation of SharePoint environment.
Migration to SharePoint 2013 – Theory and practice
1. Migration to SharePoint 2013 - theory and practice…
NICKI BORELL, EXPERTS INSIDE
SHAREPOINT AND PROJECT CONFERENCE ADRIATICS 2013
ZAGREB, NOVEMBER 27-28 2013
4. Migration to SharePoint
2013
Theory and practice…
Migration (Latin: migratio) from Wikipedia:
• Gene migration, a process in evolution and population genetics
• Animal migration, the travelling of long distances in search of a new habitat
• Human migration, physical movement by humans from one area to another
• Data migration, the process of transferring data between storage types, formats, or computer
systems
• System migration, the tasks involved when moving data and applications from current hardware to
new hardware
• Forest migration, the movement of large seed plant dominated communities in geographical space
over time
• In computing and consumer electronics an upgrade is generally a replacement
5. Preparing to Upgrade or Migrate to SharePoint
2010/SharePoint 2013
Migrating Legacy On-Premise Solutions to
SharePoint Online and Windows Azure
Migration Strategies for Search in
SharePoint 2013
Migrating to SharePoint Online in
Office 365 - Strategy and Best
Practices
SharePoint 2013
Upgrade Deep Dive
SharePoint 2013 Upgrade
Overview
6.
7. Past & Future
Issues:
- Difficult problems
- Not all components can be upgraded
- Long running upgrade process
- Not clear what exactly happens during upgrade – only a
logfile at the end
- All or nothing migration
8. Past & Future
Lessons learned:
-
“site collection health checks”
database attached update for almost all Service Applications
“self-service site collection upgrade”
-
-
Separating “Site Collection Upgrade” and “Database Upgrade”
“cross-version services connections”
“throttles and queue management”
ULS Logs
Upgrade Evaluation
9. Some Facts
No in place Upgrade
available
DB attached Upgrade is
the only way without
using 3th Party Tools or
code
/14 and /15 hives will be
installed
No visual Upgrade
based on „switch
Stylesheets etc.“. Site
Collections are running
in /14 or /15 hive
Features and Templates
from SP2010 still work
“upgrade job in
process” - no way to
remove during run
NO Rollback
No problems with RBS,
Upgrade is a DB
Schema Update
SPDesigner 2010 still
works for some SP2013
parts – unsupoorted
http://365.webbrewers.com/
blog/Lists/Posts/Post.aspx
?ID=25
http://support.microsoft.co
m/kb/2553382
11. The Microsoft Way
SHAREPOINT
2013 UPGRADE
PROCESS
PREPARE
UPGRADE DATABASES
UPGRADE SITES
• GATHER INFORMATION AND
CLEAN UP 2010 FARM
• PREPARE 2013 FARM
• COPY DATABASES
• UPGRADE SERVICE
APPLICATION DATABASES
• CREATE WEB APPLICATIONS AND
APPLY CUSTOMIZATIONS
• UPGRADE CONTENT DATABASES
• RUN SITE COLLECTION HEALTH
CHECKS
• CREATE AN UPGRADE
EVALUATION SITE COLLECTION
• UPGRADE A SITE COLLECTION
14. Site Collection Upgrade
• Upgrade databases now and site collections later
• No major changes to existing experience
• Health rules help prevent failed site collection upgrades
• Per site collection logs
• Upgrade Evaluation Site to preview upgrade
Upgrade Queuing and Throttling
• Upgrade Queues
•Each SPSite upgrade is queued
•Can be removed from queue
•Stays in queue on unexpected failures
•Farm admin has control
• Upgrade Throttles
•Throttle per web application
•Throttle per content database
•Upgrade Timer Jobs
•Farm admin override
Unsupported In 14 Mode
• All new SharePoint ’15’ specific features
• 2010 Web Analytics
•Existing web analytics features must be removed
•New web analytics features supported only in 15 mode
• 2010 Office Web Applications
•Replaced with ’15’ Office Web Applications for both 14 and 15 modes
•PowerPoint Broadcast Sites must be removed-use Lync instead
You should know, that…
Customizations Upgrade
• Existing customizations older than SharePoint 2010
may work, but change delta is much higher
• Existing SharePoint 2010 customizations should
normally work without change in 14 mode but may
require changes to work in 15 mode (Visual
customizations (i.e. JS/CSS))
• New SharePoint ’15’ customizations not available in
14 mode
Services Upgrade
• Most services databases can be upgraded
• ’15’ Office Web Applications (WAC) on
separate farm
• User Defined Functions no longer work in
Excel Services
• Secure Store passwords can be maintained
19. Sources
Upgrade to SharePoint 2013:
http://technet.microsoft.com/en-us/library/cc303420(v=office.15)
Use a trial upgrade to SharePoint
2013 to find potential issues
Best practices for upgrading to SharePoint 2013
Overview of the upgrade process to SharePoint 2013
Checklist for database-attach upgrade (SharePoint 2013)
Create a plan for current customizations during upgrade to SharePoint 2013
Migrate from classic-mode to claims-based authentication in SharePoint 2013
Plan for site collection upgrades in SharePoint 2013
Services upgrade overview for SharePoint Server 2013
Upgrade databases from SharePoint 2010 to
SharePoint 2013
Troubleshoot database upgrade issues in SharePoint 2013