[dropcap][/dropcap] [dropcap][/dropcap]How to we get the SharePoint 2010 upgraded to 2013?
We do not have anymore inplace upgrade, so we need to bring the databases over to SharePoint 2013 Farm. So we need to have SharePoint 2013 farm built, services setup and server distribution before the upgrade.
What are the high level upgrade Stages?
What service applications can be upgraded?
Only a few of the service applications below can be upgraded.
- Managed Metadata
- Business Data Connectivity
- Secure Store
- Search Administration
- User Profile – Profile, social and sync databases
How are the service applications upgraded?
Restore the database from 2010 farm and in required rename it while restoring to any new 2013 service app database naming convention. Then can use this database name while creating new service application either from CA or with
How can we upgrade upgrade Site Collections or Content databases?
This involves three steps: Get the databases restores in SQL server. Mount the content database associated with web application. Upgrade the site collection from the sites banner. Or upgrade the content database and the associated site collections with PowerShell.
While upgrading consider – how are the cpu, memory and disk IO doing as the process running on the servers. Before we do the production upgrade we need to have an test or stage 2013 farm where we can run and note how long the upgrade can take will it help if we run the upgrade parallel. Upgrade performance is very crucial while planning for production upgrade.
We can upgrade as an administration all the content databases, and as a user they can upgrade their site collections by clicking on the upgrade banner.
We will see other detailed admin upgrade commands and considerations in the following post.