EV to PST
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.
The following is a list of requirements.
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.
The Native Format Import module, and if needed, the post processing module should be installed on a bridgehead server.
An AD Collector module should be installed so that it can collect user-level information for the migration project.
One or more staging areas should be setup, of an appropriate size and should be excluded from virus scanners.
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.
The Stage 2 workflows should be reviewed, and if necessary, customized to meet the needs of the project.
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 Migration Manager for Email Archives 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 Migration Manager for Email Archives Core has not had contact with the module) and that the module versions are as expected.
Select and enable one or more domains for synchronization.
Add the Enterprise Vault source environment.
Create a PST link, and ensure that the Source modules are associated with it. The PST Output Path in this case is not used, so any UNC path can be given.
With the PST link selected, go to the PST tab, and set the watermarks for the PST Output location.
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).
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 is 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.
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.
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.
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.
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.
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.
The following general considerations should be taken into account for this type of migration: