Hi there,

we need to copy our current Intranet Site Collection to our development environment in order to test a couple of new custom solutions.

The intranet site collection has Variations enabled (English / German language) and uses managed metadata navigation with a site collection term set.

I performed a site collection backup and restored the site collection on our dev environment. Contents are displayed ok, but the managed metadata navigation is empty. I used a powershell script to transfer all information from the managed metadata service application to our dev system as well - but it seems that this does not include the local term sets. I hoped it would copy the values with the backup / restore, but again nothing available.

Any ideas how I could restore this managed metadate navigation? We are talking about 163 entries in each language - and I wouldn't like to create them all manually ;-)

Update:

As mentioned, I used a similar script as described here to transfer the managed metadata terms to my dev system.

I now had a closer look at the database and indeed: the information for my managed metadata navigation is listed correctly in the database for the Managed Metadata Service Application - just like in the prod DB.

Now I wonder whether I just need to fix a link in order to get things to work. Any ideas?
However, I think it is strange I can't even view the Term Group (Site Collection - inside) in the term store management tool.

Hi,

As I understand, you encountered the issue after you transferred the managed metadata terms to your dev system by Powershell script.

You have exported/imported the site collection and managed navigation, then you should link navigation to the site collection in the new environment. So you can do this by Powershell script, the article below gives you the details about how to backup and restore the site collection with the managed metadata service by Powershell script, you can focus on how to attach to site collection.

http://www.herlitz.nu/2014/11/05/restoring-a-backed-up-site-collection-with-managed-navigation-in-another-web-application

From your screenshot, you had the error when you went to the navigation setting, and it provided you the correlation ID. You can search in the ULS log with the correlation ID to see the details about the error.

There is a similar case:

https://social.msdn.microsoft.com/Forums/office/en-US/755792b1-3658-440c-8596-4ec79d50ebe1/backuprestore-my-managed-metadata-service-term-store-hierarchy-from-my-staging-environment-to?forum=sharepointdevelopment

Best regards,                                  

Sara Fan

Hi Sara,

thanks for your help. I managed to solve the issue following those two blog posts (which basically do the same like the one mentioned by you - but yours is more comprehensive) shortly before you posted the correct solution:

http://blogs.msdn.com/b/bettertogether/archive/2014/10/04/site-collection-backup-restore-when-using-local-term-groups.aspx

http://blogs.technet.com/b/fromthefield/archive/2014/10/13/local-mms-term-stores-and-backup-restore-spsite.aspx

We really had to reconnect the site collection term group again to the site collection and everything worked smoothly.

My Code looked like this (with a bit manual effort, so could still be optimized):

$site = Get-SPSite NewSiteCollectionURL

$taxonomySession = Get-SPTaxonomySession -Site $site
$termStore = $taxonomySession.TermStores["Managed Metadata Service"]

#Group name can be derived from Managed Metadata database, table ECMGroups
$group1 = $termStore.Groups['Site Collection - ahr144s-sites-sptrain']
$group1 #note down the old site collection ID in SiteCollectionAccessIDs
$group1.AddSiteCollectionAccess($site.Id)
$group1.DeleteSiteCollectionAccess('GUID of old site collection')
$group1.TermStore.CommitAll()