Enterprise Vault File System (FSA) Migration

It feels like a long time since I wrote anything in here.  It’s been amazingly busy over the last few months and blogging seems to have taken a back seat in preference of getting other work done. (shame on me!)

A customer came to us recently with a request I haven’t blogged about before, and I thought it was a good reason to write something.  The customer has what I would call a crippled Enterprise Vault infrastructure and they want their data off, and fast.  They have a combination of Email and File System archives.  I’ve waffled on about how easy we make the EV mail migration side of things before, but I’ve never mentioned that we support Enterprise Vault FSA migration.


Show me the way

So, you’ve got a few Enterprise Vault FSA Archives, and you want that data out, and here you are, so let’s not keep you waiting.

PS C:\Program Files\Simply Migrate> New-SmJob -source EnterpriseVaultFileSystemArchiving -SourceInput 1FA4919CBEF34CF49BF682060EB7B653B1110000evserver1 -Target FileSystem -TargetOutput \\myserver\my_EV_Files\ -BatchId 1

So, that above cmdlet gets all of the archived files from the archive indicated in the -SourceInput parameter, and extracts them all to the folder structure they were in EV to the location indicated in the -TargetOutput parameter.  It’s really that simple.

As always, it’s per item tracking and reporting so you have the same reliable chain of custody reporting.

Over and out.




  1 Comment   Comment

  1. I love this, so short and sweet.
    I believe the rehydrated files from EV end up being considerately bigger on the FSA than they are in the EV archive. Is this true and by how much in percentage, can I expect the files to swell when rehydrated?


Leave a Comment