SharePoint 2010 - Move Managed Metadata Databases (MMD) between Farms

Managed metadata and taxonomy is one of the cool things in SharePoint. If you are responsible for the managment of a multi farm infrastructure with development(DEV), integration(INT) and production(PRO) systems you have to provide a solution for moving managed metadata content across different farms. I tried different approches like export/import, shared service application, etc, but none of them provide a complete solutionö. Andrew Connell is the man who can help you. In his article he describes how to move the whole service database from one farm to another.

http://www.andrewconnell.com/blog/archive/2011/06/15/sharepoint-2010-managed-metadata-movingcopying-mms-instances-term.aspx

Usually taxonomy and term store is managed and maintained on production system. If your developers need a copy of the database for testing purposes, or your project manager needs a up to date integration system, you can just move the database as described in the article.

HINT: I automated the database backup/restore process for repeating actions with MS SQL SSIS. It allows you to prepare a package with all parameters and actions required for the movement.

At the end you get a "click once" deployment between farms! Quite nice..

SharePoint 2010 - Move Nintex Workflow Databases between SharePoint farms

Some months ago my project manager came to me and asked if it is possible to move a content database from production farm to development farm. Our developers needed real content to test different extensions. I answered YES, with a big smile. BUT the I recognized, that we use Nintex Workflows. If I would only copy the SharePoint content database, all Nintex workflows would be in a inconsistent state and not functioning on development/integration farm. So I stopped smiling and started searching for a solution.

First of all: Nintex published some whitepapers about this issue.

http://connect.nintex.com/files/folders/tutorials_and_how_tos_nw2010/entry20197.aspx
 http://connect.nintex.com/files/folders/technical_and_white_papers_nw2010/entry17226.aspx

Based on this inputs I created a approch to move our content and Nintex Workflow databases:

Production:

1. Backup SharePoint Content Database
2. Backup Nintex Database
3. Both have to be in Sync. No Workflow changes while Backup

Development/Integration:

1. Restore SharePoint Content Database
2. Delete existing Nintex Database
3. Restore Nintex Database
4. Mount SharePoint Database
5. Perform IIS Reset
6. Change license key to development key

 

HINT: I automated the database backup/restore process for repeating actions with MS SQL SSIS. It allows you to prepare a package with all parameters and actions required for the movement.

At the end you get a "click once" Nintex database deployment between farms! Quite nice..