Introduction

This article explains what the requirements are for an EV to PST 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

The Native Format Import  module, and if needed, the post processing module should be installed on a bridgehead server.

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.

PST Output Area created

One or more PST Output areas should be setup, of an appropriate size and should be excluded from virus scanners. It is this location where ‘finalized’ PSTs will be place.

PST Temporary Path created

A PST Temporary Path should be setup, of an appropriate size and should be excluded from virus scanners. It is this location where ‘temporary” PSTs will be placed.

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 (indicating 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.

Create PST Link

Screen: Links
Create a PST link, and ensure that the Target modules are associated with it.  Configure the PST Output Path, and PST Temporary Path.

Set Watermarks for Output Path & Temporary Path

Screen: Links
With the PST link selected, go to the PST tab, and set the watermarks for the PST Output location.

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 (this will only confuse things later).

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.
Additional space may be required on the staging area as temporary PST files are created on there, before being placed on the PST Output Path. It is recommended to use double the normal size of staging area. (Or use a PST Temporary Path)

Configuring High and Low Watermarks

Screen: Links
It is recommended to set the high and low watermarks to around 25% of the available disk space. For example if there is 200 Gb of disk allocated for the staging area, and one link, then the low watermark should be 50 Gb and the high watermark should be 150 Gb. Having this additional free space allows for some room for operating with the temporary PST files that reside on the staging area.

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 screen, enter a folder name to be used for placing the items into the target archive.

Configure File Name Policy

Screen: File Name Policy
Review and configure any required PST file name policy. This is the naming standard which will be used when placing the PST file on to the PST Output Path.

Change PST Roll-Over Threshold

Screen: Links
The default PST Rollover threshold is 2 Gb. If it is required to adjust this, it can be done on the Links page when the PST link has been selected.

Map one or more Containers

Screen: Bulk Mapping
One or more containers can now be mapped and migration can begin. It is often easiest to use a filter on the bulk mapping screen to show only Enterprise Vault as a source.

General Considerations

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

  • None at this time
Print Friendly, PDF & Email