Migrating a journal archive
Migrating a journal archive can take a considerable length of time due to the size of the archive itself in the source environment. It is possible to migrate journal archives to any of the supported targets, as described in the following sections.
Migrating a journal archive to PST or Exchange
When migrating a journal archive out of Enterprise Vault to a non-Enterprise Vault target environment, it is recommended to make use of a new feature relating to folder splitting. Many target environments have limits on the number of items in a single folder, or perform poorly when there are a large number of items in a single folder, as is the case with PST.
|
|
NOTE: For information relating to migrating journal archives to Office 365, using Journal Splitting, see Office 365 Configuration Changes. |
|
Item |
Description |
|---|---|
|
Journal Archive Split to Folders Base Folder Name |
This is the name of the top-level folder to ingest items into in the target environment. |
|
Journal Archive Split to Folders Max Items Per Folder |
This is the number of items that should be placed in each folder before a new folder is created. |
If the migration is to take place to PST or Exchange, navigate to the System Configuration page in the Admin Interface, and configure the following settings.
|
|
NOTE: The splitting of items is performed after the Enterprise Vault Collector process has gathered metadata about the items to migrate. |
Performing the journal mapping
Once the configuration changes have been made, then the journal archive can be mapped in the normal way except that you should choose the option in the wizard to process the mapping as journal splitting.
Migrating a journal archive to Enterprise Vault
This section outlines the steps that are required in order to complete the migration of a single journal archive within Enterprise Vault to a new Vault Store.
The first section explains how to perform the migration using a single container mapping. It is necessary to perform these steps if the migration is from a version of Enterprise Vault prior to 10.0.4. In Enterprise Vault 10.0.4, changes were made to the Enterprise Vault API meaning that a new way can be used to extract and ingest data. The second part of this topic explains how to perform a journal archive migration if Enterprise Vault 10.0.4 or later is the source.