- Database Attach (Recommended)
- Improved over SP2010 database attach
- 2010 –> 2013
- In-Place no longer supported
- Third Party Tool
- Any version -> Any version
Database Attach upgrade approach is very standard and recommended for migration from SharePoint 2010 to SharePoint 2013. We follow this approach though out this article.
Database attach upgrade approach
Prepare for the Up gradation
- Investigate existing farm and Gather Information
- Gather Settings
- Alternate Access Mapping (intranet.heartwareinc.com)
- Authentication Providers and Authentication Mode
- Incoming and Outgoing e-mail settings
- From central administration
- All WSPs [Web parts, workflows, user controls, Master pages, CSS and other deployable]
- [Note: Based on the custom solutions it may require to upgrade the codebase compatible to SharePoint 2013.]
- 3rd party tools used
- Any SSL or other certificate from central administration site
- Gather Environment Information
- Number of Sites
- Number of Databases
- Web application database
- SharePoint Service application database
- LOB application database
- Number of Users
- Clean up
- Check and repair all database consistency error
- Turn Off Web analytics Service application
- Prepare SharePoint 2013 Farm
- Install the Software
- Configure Service Applications
- Configure Farm settings
Following database types can be upgraded to SharePoint 2013 Products.
- Content Databases including My Sites (WSS_Content_ID)
- Service Application Databases
- Business data connectivity
- Manage Metadata Service
- Performance Point Service
- Secure Store Service
- Search Service Application
- User Profile Service Application
- Copy or Backup Content Databases
- Upgrade Service application database: 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 Deploy the customization
- Create and configure web application
- It is not required to create site collection in it because upgrade approach will automatically add new site collections in it.
- Deploy Customization
- Solution packages
- Custom site definitions
- Web parts
- Web services
- Web.config settings
- And others
Note: This may require code upgrade to support SharePoint 2013.
- Upgrade Content Databases
- Use the Mount-SPContentDatabase cmdlet in Windows PowerShell to upgrade the databases.
- Run site collection health checks
- Create an upgrade evaluation site collection
- Upgrade a site collection
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.
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.
After verifying that the site is ready, site collection administrators can upgrade their site collection to the new user interface.
Note: For My Sites, when you are ready to upgrade them, upgrade the My Site host site collection before allowing user access to their My Sites. When users browse to their My Sites after the My Site host is upgraded, their site collections are upgraded automatically.