Simply Migrate - Enterprise Vault Archive Migration

This article describes migrating an Enterprise Vault Archive to Mimecast using the Simply Migrate Management Shell.

To ensure that the Simply Migrate client has been correctly set, please follow the steps outlined in the following article, Data Retention - Simply Migrate - Post Installation Guide.

Connecting to the Database Source

First, connect to the database source of the Enterprise Vault SQL server. To do this, use the following PowerShell cmdlet.

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

Creating the Job

The next step is to create the job to migrate a single Enterprise Vault archive to a Mimecast user archive; this is done by using the following PowerShell commandlet.

New-SmJob -Source EnterpriseVault -SourceInput 12D1D53C97908DD408A3E0702B2810A0E1110000evserver1 -Target Mimecast -TargetOutput [e-mail] -tags 'EV Archive Migration' -Batchid 1

The above script will create a job for a single user archive migration found in Enterprise Vault; see the table below for a breakdown of the commands used.
 

Command	Value Description
New-SmJob	The commandlet that is required to create a new job.
Source	The data source to be migrated: in the above example, we have selected EnterpriseVault.
SourceInput	A defining parameter for the source technology archives, we selected the ArchiveID of the Enterprise Vault user archive in the above example. (12D1D53C97908DD408A3E0702B2810A0E1110000evserver1)
Target	The target technology the archive data is being migrated to, in this case, either Mimecast or PSTFile. In the above example, we have selected Mimecast.
TargetOutput	For the email address of the target Mimecast archive, in the above example, we selected [e-mail].
Tags	The method to expose, categorize, or otherwise 'tag' jobs. In the above example, we selected to use (EV Archive Migration)
BatchID	The ID of the batch the job will be assigned to.  In this case, 1.

Simply Migrate offers a script to report on all Enterprise Vault archives and resolve them against user email addresses. The result is a CSV file that can be used to automate job creation, as shown below:

Get-SmEVStatistics -archiveTypesSelected UsersOnly -lookupEmailInAD -pathToReport c:\temp\EVData.csv

$EvData = Import-CSV c:\temp\EVData.csv

foreach ($uA in $EvData) {

New-SmJob -Source EnterpriseVault -SourceInput $($uA.ArchiveID) -Target Mimecast -TargetOutput $($uA.Email) -Tags "EV Archive Migration" -BatchId 1
}

The above script will create a job for all user archives in Enterprise Vault; see the table below for a breakdown of the commands used.
 

Command	Value Description
New-SmJob	The commandlet that is required to create a new job.
Source	The data source to be migrated: in the above example, we have selected EnterpriseVault.
SourceInput	In the above example, we selected the ArchiveID of the Enterprise Vault user archive from a .CSV file as a defining parameter for the source technology archives.
Target	The target technology the archive data is being migrated to, in this case, either Mimecast or PSTFile. In the above example, we have selected Mimecast.
TargetOutput	The email address(s) of the target Mimecast archive: in the above example, we used the $uA.Email attribute from within the .CSV file to input this value.
Tags	The method to expose, categorize, or otherwise 'tag' jobs. In the above example, we selected to use (EV Archive Migration)
BatchID	The ID of the batch the job will be assigned to.  In this case, 1.

Journal Data

Enterprise Vault Journal data is another common source migrating to Mimecast. The script below exemplifies how this can be used to migrate journal data. This script will also split the journal jobs into monthly segments.

Get-SmEVStatistics -archiveTypesSelected JournalOnly -splitJournals -pathToReport c:\temp\EVJData.csv

$EvData = Import-CSV c:\temp\EVData.csv

foreach ($uA in $EvData) {

New-SmJob -Source EnterpriseVault -SourceInput $($uA.ArchiveID) -SourceOptions Journal -DateFrom $($uA.DateFrom) -DateTo $($uA.DateTo) -Target Mimecast -Tags "EV Archive Migration" -BatchId 1
}

The above script will, again, create a job for all user data found in the Enterprise Vault archive, now also including Journaling data; see the table below for a breakdown explanation of the commands used.
 

Command	Value Description
New-SmJob	The commandlet that is required to create a new job.
Source	The data source to be migrated: in the above example, we have selected EnterpriseVault.
SourceInput	In the above example, we selected the ArchiveID of the Enterprise Vault user archive from a .CSV file as a defining parameter for the source technology archives.
SourceOptions	In this case, the Journal option has been used where a P1 envelope can be created.
DateFrom	Simply Migrate attempts to break all jobs down to a more manageable size; journaling is no different. The Journal archive is split with date ranges. The DateFrom is when you would like this date range to start. In the above example, we have got the date from a $uA.DateFrom attribute within the .CSV file.
DateTo	Simply Migrate attempts to break all jobs down to a more manageable size; journaling is no different. The Journal archive is split with date ranges. The DateTo is the date you would like this date range to end. In the above example, we have got the date from a $uA.DateTo attribute within the .CSV file.
Target	The target technology the archive data is being migrated to, in this case, either Mimecast or PSTFile. In the above example, we have selected Mimecast.
TargetOutput	The email address(s) of the target Mimecast archive: in the above example, we used the $uA.Email attribute from within the .CSV file to input this value.
Tags	The method to expose, categorize, or otherwise 'tag' jobs. In the above example, we selected to use (EV Archive Migration)
BatchID	The ID of the batch the job will be assigned to.  In this case, 1.