Thursday, 9 May 2013

SharePoint 2010 to 2013 Migration


This model describes the required steps to upgrade from SharePoint Foundation 2010 or SharePoint Server 2010 to SharePoint Foundation 2013 or SharePoint Server 2013. The database-attach method is the only supported method for upgrading from SharePoint 2010 Products to SharePoint 2013 Products. Information about the Business Data Connectivity service application applies to both SharePoint Server 2013 and SharePoint Foundation 2013. Information about all other service applications and about My Sites applies only to SharePoint Server 2013.

1.   Prepare

·          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 elimination potential upgrade errors. Try out upgrade in a test farm. See the model poster SharePoint 2013 Products – Testing Upgrade for information about how to perform the test upgrade.



·         Prepare 2013 farm
For a database-attach upgrade, you upgrade the data and sites on a separate farm from your original farm. In this step, you set up and configure this new farm. The new farm is used to upgrade the data and sites, and becomes the farm that users will connect to going forward.
Important Review the system requirements and administrative accounts needed for SharePoint 2013 Products.




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




·         Copy databases
To perform a database-attach upgrade, you copy your databases from your original farm to your new farm.




·         Upgrade service application databases
Use Windows PowerShell cmdlets to create new service applications and upgrade the service application databases. You must also create proxies for the upgraded service applications and add the new service application proxies to the default proxy group.

·         Create web applications and apply customizations
Use Windows PowerShell cmdlets to create new service applications and upgrade the service application databases. You must also create proxies for the upgraded service applications and add the new service application proxies to the default proxy group.

·         Create web applications and apply customizations
Create and configure web applications Create a web application for each web application in your 2010 farm. Do not create site collections. Those will be created automatically when you upgrade the content databases.
Reapply customizations Install necessary customizations for your environment: solution packages, custom site definitions, style sheets, Web Parts, Web services, features, solutions, assemblies, Web.config changes, form templates, and so on.
Verify Use the Test-SPContentDatabase cmdlet in Windows PowerShell to verify that the new environment has all of the components you need before you upgrade any databases.

·         Upgrade content databases
Now that the databases are available in the new farm, you can attach and upgrade them. Although this upgrades the data, it does not upgrade the user interface for the sites contained in the databases. Use the Mount-SPContentDatabase cmdlet in Windows PowerShell to upgrade the databases.

3.   Upgrade sites
Now that the databases have been upgraded, site collection administrators can upgrade their sites. The following steps are performed from the Site Settings page in the site collection.

·         Run site collection health checks
Before upgrading, site collection administrators can use the site collection health checker to identify and address potential issues in their site collections. Health checks are also run automatically before upgrade.




·         Create an upgrade evaluation site collection
Site collection administrators can also request an upgrade evaluation site collection – a separate copy of the site collection upgraded to the new user interface. This site is used to preview the new user interface so that the administrator can address issues before upgrading the site collection.



·         Upgrade a site collection
After verifying that the site is ready, site collection administrators can upgrade their site collection to the new user interface.


No comments:

Post a Comment