Simply Migrate - Migrate An Enterprise Vault User Archive to PST

This article will provide an overview of how to migrate a Veritas Enterprise Vault User Archive to a PST file using the Simply Migrate Management Shell. 
 

Note:

To ensure that permissions are set correctly, follow the steps outlined in the Enterprise Vault Permissions article.

What you need to create a job

New-Simply Migrate Job	The cmdlet used to create a new job
Source	The source of the data, in the below example, we used EnterpriseVault.
SourceInput	The Enterprise Vault ArchiveID. In the below example, we used the ArchiveID of the Enterprise Vault user Archive (12D1D53C97908DD408A3E0702B2810A0E1110000evserver1).
Target	The Target technology is being migrated to. Mimecast API or PSTFile. In the below example, we have chosen PSTFile.
TargetOutput	In the below example, this is the name of the PST file that will be created by this job. The path and file name ("F:\PST Data\PSTFile.pst").
MaxPSTSize	The maximum size of the PST file that will be created before rolling over to a new PST file, with a numeric representation. We used (5120) in the below example, indicating a 5Gb PST limit.
BatchID	The BatchID of the Batch the job will be assigned to.
Tags	Tags are a method to expose, categorize, or as the term indicates, tag jobs. In the below example, we chose to use ("PST Extract").

As this is a source that contains a database you would need to first load the connection string to the EV SQL server:

Set-SmConfiguration -EVDirectoryDB "Server=SMLABSQL\SMArchives;Database=EnterpriseVaultDirectory;Trusted_Connection=True"

Creating a job

The job syntax for creating an Enterprise Vault export to PST is shown here:

New-SmJob -Source EnterpriseVault -SourceInput 12D1D53C97908DD408A3E0702B2810A0E1110000evserver1 -Target PSTFile -TargetOutput "F:\PST Data\PSTFile.pst" -MaxPSTSize 5120 -BatchId 1 -Tags "PST Extract"