successful migration to sharepoint 2013 - planning considerations & migration strategies
DESCRIPTION
Successful Migration to SharePoint 2013 - Planning Considerations & Migration StrategiesTRANSCRIPT
| Lausanne
Successful Migration to SharePoint 2013 - Planning Considerations & Migration StrategiesRoberto V. DelgadoSr. Technical Solutions Professional @AvePoint
Agenda
Design Goals for SharePoint 2013 5’UpgradesFarm Upgrade Overview 10’Site Collection Upgrades 20’Upgrade and Migration Strategies5’General Recommendations 10’Q&A 10’
About me: Roberto V. Delgado
www.docave.com
Text/Icon/Pic
Design Goals for 2013 Upgrades
Safer 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
| Lausanne
Farm Upgrade Overview
Prepare
Detach and Re-attach Databases
PowerShell Command
Recap Upgrade Stages
Demo: Farm Upgrade
| Lausanne
Site Collection Upgrades
Deferred Site Collection UpgradeEliminate big bang upgrades
Upgrade 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
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
Demo: Site Collection Upgrade
Summary of Farm Upgrade1. Backup everything2. Upgrade services firstSearch Administration databaseProfile, Social, and Sync databasesManaged Metadata/Taxonomy databaseSecure 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 databasesSite collection upgrade automatically deferred
4. Upgrade site collections at your leisure
Summary of Farm Upgrade
5. Confirm successful upgrade state• Verify services and content rendering• Fix issues if necessary
6. 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 administratorsOld, NewVersion, or 15 will prevent 2010 site collection creation except for farm administrators, but
will allow upgrade of 2010 site collections by site collection adminsAll, AllVersions, or “14,15” will allow both 2010 and 2013 site collection creation and upgrade by
site collection admins
7. Re-index existing content
| Lausanne
Upgrade and Migration Strategies
Upgrade and Migration Strategies• Upgrade to next version
• Read-only databases• Parallel database upgrades (Plan for performance during upgrade)
• Jump to the latest version (i.e from MOSS 2007 or SPS2003)
• Requires 3rd party tool
• Migrate to the Cloud• Manual• 3rd party tool
Migration with Third Party Tools
ConsPros
Any size environment, from single server farm to large, distributed farms
Restructuring content Preservation of any
metadata or security Mappings (Templates,
users, field types, content types…)
Direct migration from 2007 to 2013
Pre-scan to determine content & customizations
Granular migration
Virtually no downtime
Applicable to non-SharePoint repositories
Incremental migrations
Costs associated with purchasing of additional software
Training
Best For
SharePoint Administrator installs the new version on separate hardware or a separate farm, and migrates content and users using 3rd Party Tool
| Lausanne
General Recommendations
Best practices• Clean up an environment before an upgrade
Unused site collections and subwebs Check large lists Consider moving site collections into separate databases Remove unused templates, features and Web Parts Make structural changes
• Create a plan for current customizations during upgrade• Plan for authentication
• CMA (Classic) to CBA (Claims)• Plan for performance during upgrade• Create a communication plan for the upgrade•TEST
| Lausanne
Q&A
© 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.
© 2013 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.