Enterprise Vault 10.0.2 & SharePoint 2007 Upgrade to 2010/2013

[Surinder_-_Cent]

Hi,

We have a SharePoint 2007 farm, that has archived content, which will be upgarded to SharePoint 2010/2013.

Can the archived content be migrated or doe sit need to be unarchived first?

Surinder

[TonySterling · Accepted solution]

Based on this previous post seems like it will need to be restored.

https://www-secure.symantec.com/connect/forums/enterprise-vault-9-migration-sharepoint-2007-2010#comment-7840711

I wanted to reply to my own post with answers on this topic. After starting a case with Symantec it was explained currently the only migraiton route is to:

1) Recover all contect using the EVSPshortcutmanager.exe utility.

2) Once the data has been recovered in full, use Sharepoint to migrate the Content Databse to SP 2010.

3) Run the Content Database Upgrade.

4) Deleted the Orignal Archive, then in EV target the new user's site/collection.

5) Allow EV to re-archive the data and create new stubs. This creates a new archive for the user.

I have tested this method and it works. 

Lastly, I was also able to upgrade the users data with an unsupported migraiton method. I updated the TLSPathURL and SharePointSite ID in the SQL table for "SharepointTLSTarget". I refreshed the VAC and saw it moved the users archive to the new Site, then I ran the EVSPShortcutmanager.exe with -recall and it recalled and re-archived all data. Keep in mind, this is NOT supported currently, but cuts out a tremendous amount of work. 

You can find more info on the EVSPShortcutManager here:

About EVSPShortcutManager

Article:HOWTO108700

|

Created: 2015-01-09

|

Updated: 2015-01-09

|

Article URL http://www.symantec.com/docs/HOWTO108700

[AndrewB]

is the sharepoint upgrade going to be in-place or are you migrating all your sites to a new SP environment?

[Surinder_-_Cent]

Thanks for the quick reply.

Tony, that's what I started to do late last week, but was hoping for a more efficient method/process.  The recall process is quite slow, and leaving approximately 2% of the content behind with errors (which I will raise Symantec).

Andrew, its a completely new environment.