Introduction

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

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

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.

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, with a potential 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. There is no need to perform a synch at this point, enabling the domain for scanning will automatically trigger a synch.

Add Source EV Environment

Screen: EV Environment
Add the Enterprise Vault source environment.

Add Target EV Environment

Screen: EV Environment
Add the Enterprise Vault target environment. This is not necessary if both the source and target are the same.

Add Retention Category Mappings

Screen: Retention Category Mappings
Map the source and target environment retention categories. If the migration is intrasite, they can be automatically created in the admin interface.

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 EV Collector module should be associated with one of the links so that shortcut building information can be gathered from the site settings in Enterprise Vault

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.

Stop the EV Provisioning task from auto-enabling users

Screen: Enterprise Vault Administration Console
Ensure that the source and target environments do not have any provisioning groups set to ‘auto enable’ users throughout the duration of the migration. This prevents users being targeted by alternating environments depending on when and which provisioning task runs.

Stop Storage Expiry running

Screen: Enterprise Vault Administration Console
Ensure that the source and target environments do not have storage expiry running. If it is enabled then it is possible that items which are collected can not be found when it is time to export them.

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:

  • Ingest speed is likely to be reduced versus the speed of export since ingesting is also going to place a load on the indexing engine on the target environment. In general do not expect the export and ingest speeds to be comparable.
  • 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.
  • An issue is currently being investigated by Symantec. Items extracted from EV 9, may not be ingested into EV 11.0.1. This affects only a small number of items. This may be addressed in the future by Symantec.
  • EVPM may have difficulty in connecting to, and processing, mailboxes which are homed on Exchange 2013. The following article may help:
    https://info.quadrotech-it.com/knowledge-base/evpm-and-exchange-2013/
  • EVPM may need to have the DS Server registry key set. The following article may help:
    https://info.quadrotech-it.com/knowledge-base/general-errors-which-evpm-can-generate-and-how-to-handle-them/
Print Friendly, PDF & Email