Introduction

This article explains what the requirements are for an EV to Exchange migration, and then covers the basic steps that should be followed to start such a migration.

Requirements

The following is a list of requirements.

Modules installed on source

The EV-type modules should be installed on each appropriate source Enterprise Vault server involved in the migration. The EV import module is not required on these machines.

Modules installed on appropriate bridgehead to reach target

Exchange and Post Processing modules are the two which are primarily needed to work with this type of migration.

AD Collector module installed

An AD Collector module should be installed so that it can collect user-level information for the migration project.

Staging Area created

One or more staging areas should be setup, of an appropriate size and should be excluded from virus scanners.

Ingest accounts configured for App Impersonation

5 accounts should be configured with Application Impersonation rights, and those accounts should be added to the credentials editor on the machine running the Exchange ingest module.

Workflows reviewed

The Stage 2 workflows should be reviewed, and if necessary, customized to meet the needs of the project.

Apply appropriate failed item threshold

It is best practice to find an appropriate failed item threshold for the project/customer and apply that at the links level. This way all mappings which are created will inherit this value.

Basic Steps

The following are the basic steps to start this type of migration.

Enable Modules

Screen: Modules
All Archive Shuttle modules must be enabled, and optionally a schedule for them defined. It is important to verify that none of the modules have a red background (this indicates that Archive Shuttle Core has not had contact with the module) and that the module versions are as expected.

Enable Domains

Screen: Active Directory
Select and enable one or more domains for synchronization.

Add EV Environment

Screen: EV Environment
Add the Enterprise Vault source environment.

Add Source Links

Screen: Links
Configure all appropriate source links. Select the links, and then click on ‘Map Modules’, create the item database(s) and enable archive gathering. Ensure there is no import module specified on the links as this may impact the process later on.

Add Target Links

Screen: Links
Add all appropriate target links. An ingest and post-processing module should be associated with each possible target Exchange Database.

Add Staging Area

Screen: Links
Ensure that the Default Staging Area is configured correctly. Depending on the migration, the free space, and the number of vault stores being used as the source for the migration, the ‘high water mark’ can be adjusted upwards.

Configure Folder-Less Item Handling

Screen: System Configuration
Many versions of Enterprise Vault allow archiving of items in a folder-less area called the Top Of Information Store. On the System Configuration, enter a folder name to be used for placing the items in the target archive.

Ensure AIP/EWS is configured correctly

Screen: System Configuration
Ensure that the migration providers are listed in the required order and that the AutoDiscoverURL is specified if required. The account which is to be used for ingest needs to have Application Impersonation rights. This article will help with configuring that.

Consider disabling reminders for appointments in the past

Screen: System Configuration -> Exchange Import Module
Consider enabling the option to ‘Disable reminders for appointments in the past’ this will prevent pop-ups appearing from Outlook on end-user machines when old appointments are processed.

Map one or more Containers

Screen: Map Containers
One or more containers can now be mapped and migration can begin.

General Considerations

The following general considerations should be taken into account for this type of migration:

    • When migrating from a pre EV10.0.3 system extraction of data may be slower than expected if Enterprise Vault Collections have been used. Access to the data inside the CAB file is single threaded. This issue does not exist in Enterprise Vault 10.0.3 and later.
Print Friendly, PDF & Email