This article explains what the requirements are for an EV to Proofpoint migration, and then covers the basic steps that should be followed to start such a migration. When doing a migration to Proofpoint we make use of PST files as intermediate step in getting the data into Proofpoint.
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.
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.
The following are the basic steps to start this type of migration.
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.
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
Create a PST link, and ensure that the Target modules are associated with it. Configure the PST Output Path and the PST Temporary Path.
Set Watermarks for Output Path & Temporary Path
With the PST link selected, go to the PST tab, and set the watermarks for the PST Output location.
Update System Configuration
Screen: Native Format Import, System Configuration
Ensure that the option ‘Stamps a header to imported messages for Proofpoint to identify message source’ is selected in the System Configuration for the Native Format Import module.
Add Source 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
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.
Map one or more Containers
Screen: Bulk Mapping
One or more containers can now be mapped and migration started.
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.
- When choosing a PST filename policy for Mailbox Archives ensure that SAMAccountName is used in the definition.
- Set the PST Rollover Threshold to no more than 4 Gb.
- When migrating Journal Archives, it is recommended to use data-based filters to allow greater control over the mappings.