1. Migration to SharePoint 2013
---
Testing
Alex Windel Senior Premier Field Engineer Microsoft Corporation
9/18/2018

2. A G E N D A Migration Phases Upgrade Process and Requirements
Testing a Migration
9/18/2018

3. Phases – SharePoint Migration
P1 Assessment & Planning
P2 Testing, Validation & Operations
P3 Core Deployment

4. Phases – SharePoint Migration
P4 Content Migration
P5 Training & Support

5. Upgrade Process
Basically the same as 2007 to 2010 upgrade stages using database-attach method.
Typical 2010 to 2013 upgrade process

6. 2010 or earlier SharePoint products must not be installed
Upgrade Requirements
2010 or earlier SharePoint products must not be installed
To use existing 2010 SharePoint Farm hardware:
Back up your farm using SharePoint backup tools
Verify your backup
Verify SharePoint 2010 or earlier is not installed
Uninstall dependencies like Project Server and language packs
The minimum version required to upgrade content from SharePoint 2010 to SharePoint 2013 is SharePoint 2010 with Service Pack 1.

7. Database Attach Upgrade
Upgrade Methods
Database Attach Upgrade
Only available method for version to version (V2V) upgrades
Works for both version to version (V2V) and build to build (B2B) upgrades
Works for content and services databases
In-Place Farm Upgrade
Only available for build to build (B2B) upgrades

8. Upgrade content and service applications
Service Applications Upgrade:
Service applications and content
Default database name
Business Data Connectivity
BDC_Service_DB_ID
Managed Metadata
Managed Metadata Service_ID
PerformancePoint
PerformancePoint Service Application_ID
Search Administration
Search_Service_Application_DB_ID
Secure Store
Secure_Store_Service_DB_ID
User Profile: Profile and Social databases
User Profile Service Application_ProfileDB_ID
User Profile Service Application_SocialDB_ID
User Profile Service Application_SyncDB_ID

9. Upgrade content and service applications (cont)
The Three Rules of (successful) SharePoint 2013 Migration:
Rule 1: If you upgrade both an MMS and UPA, the MMS must be upgraded before the UPA.
Rule 2: Services upgrade must finish before content and personal sites upgrade.
Rule 3: After a DB schema upgrade through database attach, the My Site Host must be upgraded to SharePoint 2013 before any of the Personal Sites

10. Deferred Site Collection Upgrade
Allows existing 2010 site collections to work unchanged in SP2013
No SharePoint 2010 installation required
SP2013 has all required SharePoint 2010 files included
Deep backwards compatibility
All 14 features side by side with 15 ones
Existing customizations should just work
Default state for all sites in upgraded databses
Cannot be forced automatically on database upgrade

11. Upgrade Related PowerShell Commands
Content Database
Mount-SPContentDatabase
Test-SPContentDatabase
Upgrade-SPContentDatabase
Test-SPSite
Site
Repair-SPSite
Upgrade-SPSite
Request-SPUpgradeEvaluationSiteCollection
Farm
Upgrade-SPFarm
Queue Management
Get-SPSiteUpgradeSession
Remove-SPSiteUpgradeSession
Services
New-SPBusinessDataCatalogServiceApplication
Restore-SPEnterpriseSearchServiceApplication Upgrade-SPEnterpriseSearchServiceApplication
Upgrade-SPEnterpriseSearchServiceApplicationSiteSettings
New-SPMetadataServiceApplication
New-SPPerformancePointServiceApplication
New-SPProfileServiceApplication
New-SPProjectServiceApplication
New-New-SPSecureStoreApplication
New-SPSubscriptionSettingsServiceApplication

12. Content upgrade Site collection upgrade
Mount-SPContentDatabase
Initiates Content Database schema upgrade
Runs internal consistency/orphans check
Runs web application compatibility checks
Site collection upgrade
Upgrade-SPSite
Used for both build to build and version to version upgrades
Use -VersionUpgrade option to change from 14 to 15 mode
Can be used in parallel with other site collection upgrades

13. Testing a Migration Collect Data about Source Farm
Gather data about source farm
Review Health Analyzer issues, trace logs, event logs…
9/18/2018

14. Testing a Migration Create source test environment
Back up and restore source content databases from production source farm to new test environment
Transfer service applications to source test environment then use OOB farm backup/restore tools
Install latest SharePoint service pack for source test platform
Create Full farm Backup of new test environment
Perform all migration testing with new (source) test environment
Verify versions with queries like the ones below:
9/18/2018

15. Testing a Migration Clean Up Database Orphans
Repair database orphans through health analyzer rule:
Repair database orphans through stsadm databaserepair
The databaserepair option provides result with any corruption in XML format. This primarily lists the objects that do not have any parent. This includes sites, webs, lists, list items or documents. The command also has ability to check for any corrupt permission scopes. The deletecorruption option removes such orphan items.
9/18/2018

16. Testing a Migration Clean Up (continued)
PowerShell cmdlet Get-SPContentDatabase can be used with the .Repair method to repair databases. The .Repair method has either a true or a false flag. True flag repairs the corruption while False flag just reports the corruption.
9/18/2018

17. Testing a Migration Clean Up Deleted Sites & Unused Sites/Webs
Remove deleted site
With SharePoint 2010 Service Pack 1, a new cmdlet Remove-SPDeletedSite is introduced. This cmdlet lets permanently remove a deleted site collection from the farm.
Delete unused sites and webs
Use the Remove-SPSite and Remove-SPWeb cmdlets to remove unused site collections and webs to reduce overhead of upgrade as well as storage overhead.
9/18/2018

18. Testing a Migration
Clean Up Recycle Bins and Unused Templates, Features & Web Parts
Clean up recycle bin’s on source platform
Remove PowerPoint Broadcast sites
These sites and templates are not available in SharePoint 2013.
9/18/2018

19. Microsoft Confidential - For Internal Use Only
Testing a Migration
Check if Language Packs need to be installed on target platform
If the SharePoint 2010 version uses language packs, the designated language packs must be present in the SharePoint 2013 environment.
Language check via DB query
9/18/2018
Microsoft Confidential - For Internal Use Only

20. Testing a Migration
Check if any Cross-domain or Cross-forest upgrade will occur
If you are moving content databases across domains or forests or to another environment that has different service accounts, make sure that the permissions for the service accounts are still correct before you attach the databases.
Check Event Receivers in source test environment
Use a DB Query similar to the one below:
9/18/2018

21. Testing a Migration Convert to Claims Authentication
As SharePoint 2013 requires Claims authentication, when Test-SPContentDatabase runs against a content database that has classic authentication, the following message is logged:
9/18/2018

22. Testing a Migration Migrate from Classic Mode to Claims Mode
Migrate from classic to claims through PowerShell. The steps include defining the variables, setting the web application with a new authentication provider, provide permissions to the administrator and migrate the users.
9/18/2018

23. Testing a Migration Build SP2013 test environment
For the target platform, use a build template
Use the same build template for production later
Use deployment scripts whenever possible
9/18/2018

24. Testing a Migration
Run Test-SPContentDatabase against all content databases
Use –ExtendedCheck and –ShowLocation switch !
Record and resolve ALL migration blocking issues returned via Test-SPContentDatabase
9/18/2018

25. Testing a Migration
After resolution of migration blocking issues, perform a load test
VS2013 or VS2012 Update 2 Ultimate Edition or VS Online
Use Test Recorder for SharePoint 2013 Sites
Create one or more Web Performance Tests, then a Load Test based on these
9/18/2018

26. Q & A ! Thanks! Find this slide deck at: http://docs.com/166ME
9/18/2018