Introduction
This posting walks you through the process of migrating the metadata database, from a 2010 farm to a 2013 farm. This migration is performed prior to migration of the content databases.
Preparation
This posting walks you through the process of migrating the metadata database, from a 2010 farm to a 2013 farm. This migration is performed prior to migration of the content databases.
Preparation
- Find the most recent backup of the Managed Metadata Service database, from your 2010 farm, and then copy it to the SQL Server host of your 2013 farm.
- If you already instantiated the Metadata service on your SharePoint 2013 farm, you will need to completely remove it:
- Navigate to: CA > Application Management > Service Applications > Manage service applications.
- Select the Managed Metadata Service application.
- On the Service Application ribbon, click the Delete button.
- Enable the option, Delete data associated with the Service Applications.
- Click OK.
- When completed, click OK again.
- In SQL Server Management Studio, perform a restore of your 2010 farm Managed Metadata Service database.
- After restoration, map the farm administrator and farm service accounts to the restored database both as db_owner. Also add your own administrator account as db_owner.
- In Central Administration, navigate to: Application Management > Service Applications > Manage service applications.
- On the Service Applications ribbon, click New, and then click Managed Metadata Service.
- On the Create New Managed Metadata Service dialog, enter:
- Database Name: [enter the name of the restored database].
- Other fields: as appropriate to your farm.
- After this completes, click the name of the Managed Metadata Service listed.
- Verify that the appropriate taxonomy store is shown.
- Overview of managed metadata service applications in SharePoint Server 2013
- SharePoint 2013: How to Configure Managed Metadata Service
- Configuring the SharePoint 2013 Managed Metadata service for Navigation
- This procedure performed on Windows Server 2012, SQL Server 2012, SharePoint Server 2013.
1 comment:
Thanks, great step by step description. Works also still for migration from 2013 to 2016.
Post a Comment