How to Upgrade to SharePoint 2013: Part II

Before reading this article, please go through the following article:

1. Introduction to SharePoint 2013 Upgrade: Part I

In this article we will see how to upgrade from SharePoint 2010 Products to SharePoint 2013; we use the database-attach method to upgrade. In the database-attach method, we first create and configure a SharePoint 2013 farm. Then you copy the content and service application databases from the SharePoint 2010 Products farm, and then attach and upgrade the databases. This upgrades the data to the new version. Site owners can then upgrade individual site collections.

Before starting to upgrade, you must understand what is in your SharePoint 2010 Products farm and set up a new farm based on SharePoint 2013 Products Preview.

GATHER INFORMATION and Clean up 2010 Farm

Gather information from the 2010 farm to help determine the 2013 farm topology. Gather settings and customizations, plus a performance baseline and information about the environment. Clean up your farm to eliminate potential upgrade errors. Do a trial upgrade in a test farm.

In Original farm
 

In Original farm
Gather settings Alternate access mappings Authentication providers and authentication modes that are being used Quota templates Managed paths Self-service site management settings Incoming and outgoing e-mail settings Customizations (solution packages, etc.) Certificates	Gather environment information   Number of sites Number of databases Number of users
	Clean up   Check for and repair all database consistency errors. Turn off Web Analytics service application Remove PowerPoint Broadcast Sites

PREPARE 2013 FARM

Configure Service Applications Do not use the Farm Configuration Wizard to install the following service applications: Business Data Connectivity service application Managed Metadata service application PerformancePoint Services service application Search service application Secure Store service application User Profile service application You will configure these service applications when you upgrade their databases.

Configure farm settings   Configure email settings, farm-level security and permission settings, blocked file types, usage and health data collection settings, and diagnostic logging settings.

Create the SharePoint 2013 farm

The first stage in the upgrade process creates the new SharePoint 2013 farm:

1. A server farm administrator installs SharePoint 2013 to a new farm. The administrator configures farm settings and tests the environment.

2. A server farm administrator sets the SharePoint 2010 Products farm to read-only so that users can continue to access the old farm while upgrade is in progress on the new farm.

After you have prepared the new environment, you can copy and upgrade databases.



The following database types can be upgraded to SharePoint 2013 Products Preview.


Copy the SharePoint 2010 Products databases

The second stage in the upgrade process copies the databases to the new environment. You use SQL Server Management Studio to do that.

1. With the farm and databases in read-only mode, a server farm administrator backs up the content and service application databases from the SQL Server instance on the SharePoint 2010 Products farm.

2. The server farm administrator restores a copy of the databases to the SQL Server instance on the SharePoint 2013 farm and sets the databases to read-write on the new farm.

Upgrade SharePoint 2010 Products databases and service applications

The third stage in the upgrade process upgrades the databases and service applications.

 

1. A server farm administrator configures the service applications for the new farm. The following service applications have databases that you can upgrade during this process:
   
   • SharePoint Server 2010 and SharePoint Foundation 2010
   • Business Data Connectivity service application
   • SharePoint Server 2010 only
   • Managed Metadata service application
   • PerformancePoint Services service application
   • Search service application
   • Secure Store Service application
   • User Profile service application
    

2. A server farm administrator creates a web application on the SharePoint 2013 farm for each web application on the SharePoint 2010 Products farm.

3. A server farm administrator installs all server-side customizations

4. A server farm administrator then attaches the content databases to the new farm and upgrades the content databases for those web applications.

Upgrade SharePoint 2010 Products site collections

The final stage in the upgrade process is to upgrade the site collections. In SharePoint 2013, site owners are in charge of upgrading their sites. The upgrade process for My Sites is slightly different from for other types of site collections.

Upgrade My Sites

A server farm administrator upgrades the My Site host and then individual users can upgrade their My Sites or the farm administrator can upgrade them by using Windows PowerShell. The following illustration shows four stages for the My Site host and My Sites during the upgrade process.

Upgrade other SharePoint 2010 Products site collections

Owners of all other site collections can start to upgrade their sites as soon as they see a notification on their site's home page that the new version is available. The following illustration shows four stages for a site collection during the upgrade process.

1. The site owner runs the site collection health checks to determine readiness for upgrade. The site owner addresses issues before they continue with the next step.
   
   
    

2. Optionally, the site owner requests an upgrade evaluation site collection. A timer job runs to create the site collection and the site owner receives an email message when the evaluation site collection is ready. The site owner previews the new user interface. After several days or weeks, the evaluation site collection expires and is deleted by a timer job.
   
   A server farm administrator can determine the length of time before expiration.
   
   
    

3. When the site owner is ready, the site owner starts the upgrade process. The site collection health checks are run again automatically. The site owner must address issues before upgrading. If health checks return no issues, the upgrade starts.
    

4. When the upgrade is complete, the site owner sees the Upgrade Status page that contains the status and a link to the upgrade logs. The site owner reviews the site to make sure that everything works correctly.
   
   
   

For more details please click on the MSDN Article