Simply Migrate - Enterprise Vault Archive Migration by API

This article will provide steps to migrate Enterprise Vault Archives to the Mimecast user archive using the Simply Migrate Management UI and API.

Prerequisites

Before beginning, make sure administrators have read the following prerequisite requirements below and understand the relevant criteria for the archive migration.

• Determine the SQL server name/instance that the Enterprise Vault database is on.
• Ensure the account the administrator is using has permission to read all the Enterprise Vault databases and access all archives in Enterprise Vault.
• Determine if the archives are user-only, journal-only, or a combination.
• Get the journal cut-off date from the customer.

Creating the Job

From the UI, there are two ways to create jobs; follow these steps to begin your migration.

1. Following the initial install, the Wizard will prompt the administrator to select the Source they wish to migrate - or - start the job wizard from within the Batches & Jobs view if the product has already been set up and initialized.
2. Select the Green List icon against the Batch to create the jobs and choose Job Creation Wizard from the list as shown here.

 

3. The administrator will be greeted with the Source selection. For this example, we will be choosing Enterprise Vault.

A Cog icon appears under your selection; click this to configure your Enterprise Vault settings.

4. Once clicked, the administrator will be presented with the Source Configuration page.

 

5. Enter the SQL Server name or Instance in the first box and the EnterpriseVaultDirectory in the second box. The connection string is automatically built and updated when you type these.
6. Click the Refresh button on the right of the connection string to test the connection; you should receive a Test Successful banner.
7. Click Save.
8. The administrator has some options for collecting the data from Enterprise Vault. Most of the time, these settings do not need to be changed from default. But if the partner's customer has chosen to supply a list of user archives and SMTP addresses in a CSV file, this is supported, and the administrator can choose this option and upload the .CSV.
9. Click Next.
10. The next page shows a list of the archives contained in the Enterprise Vault environment. (shown below).

We have encountered 3 different situations in the screenshot above.

1. User archives (denoted by the little person icon) have an SMTP address associated with them.
2. A user archive that has yet to be selected and needs an email address.
3. A Journal archive with no SMTP address is selected and has a little list icon next to it.

The unselected item is typically a “leaver.” A user account has left the organization, and we could not find an SMTP address. The customer can use the Bad Address Resolution option in the banner here to upload SMTP addresses for all those missing, or in this case, type an email address into the one missing and select the archive for migration.

Controls in the banner above the Enterprise Vault archive list allow you to add filters for Dates, Jobs and handle Bad Address Resolution.

In most cases, you shouldn't need to touch any of these controls, but you will be prompted about date filters when you click the Create Jobs button, just to be sure.

Filtering the jobs will only change your view of the jobs; when you click Create Jobs, Simply Migrate will attempt to create jobs for ALL items ticked in the, not just the ones visible in the filter.

11. Clicking Create Jobs will prompt the administrator with information and the option to select a date filter.

Check that the number of jobs to be created is correct, and ensure you don’t require a date filter.

12. Click Create the jobs.

The gears start turning, and the jobs start getting created; the administrator will notice a tick is shown in the job status next to all the source files that have been selected.

If you attempt to create jobs for the same Enterprise Vault Archives (In the same batch), we have created safety measures to avoid duplication of jobs. As shown below, you will see the original Job ID and a No Entry sign indicating that the job has yet to be created because it already exists.

Congratulations, you have created your Enterprise Vault source jobs.