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 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 the next section in the Administration Guide

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.

Migrating 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.

Pre-Enterprise Vault 10.0.4 Source

Prerequisites

It is essential that the following steps have been completed prior to beginning the migration:

  • All Modules are enabled
  • Appropriate Active Directory Domains are enabled for scanning
  • An Enterprise Vault Environment has been added for migration
  • A Link Database has been created for the source archive
  • Module Mappings are configured for the source Vault Store and also the target Vault Store

Each of the above steps is described in the previous sections of this document.
The target for the journal archive migration must also:

  • Be a ‘user’ and be setup with a mailbox
  • Have a journal archive created for it, in an appropriate Vault Store
  • Be listed as a Journal Target in the Vault Administration Console

Note: The Enterprise Vault journal task is used to ingest the data in to the target journal archive container.

Map Containers – For the journal archive

The first thing to do when migrating a journal archive to a new vault store is to do a container mapping. This is slightly different to the process followed earlier in the document since we must do a ‘single container mapping’. To setup the mapping, follow these steps:

  1. Click ‘Manual Mapping’.

You will now see two lists of containers.

  1. Locate the source journal archive in the left hand list, and select the radio button next to the archive.
  1. Locate the target journal archive in the right hand list, and select the radio button next to the archive.

Note: All the normal filtering and searching is available on the Single Container Mapping screen, which can help identify the correct archives when there are many journal archives displayed on screen.

  1. Click ‘Add Mapping’.

Set Policies and Enable Migration

Once the container mapping has been selected, it is necessary to add two more components to the link, before the migration can be enabled. To setup the migration, follow these steps:

  1. Click ‘Existing Mappings’. Note: All the normal filtering and searching is available on the Existing Mapping screen, which can help identify the mapping.
  2. Locate the mapping that was created in the previous step.
  3. Select the checkbox next to the mapping.
  4. From the toolbar, select ‘Set Workflow Policy’, and choose the Journal Workflow.
  5. From the toolbar, select ‘Set Filter Policy’, and choose a filter if one is required.
  6. Finally, from the toolbar select ‘Enable for Migration’, and ‘Enable Item Gathering’.

Note: The container mapping will now look much like other mappings that may have been created. Ensure that the ‘Item Gathering’ and ‘Migration Enabled’ flags are displayed before moving on to monitoring the migration

Monitoring the Migration

Monitoring the ‘Stage 1’ synch process for a journal archive is the same as with other types of archive migration. A few minutes after setting the policies and enabling migration (see previous section), the container will appear on the ‘Stage 1 (Sync Data)’ screen in the administration console.

Performing Stage 2 and Extra Steps

Migrating a journal archive is slightly different to migrating an ordinary Enterprise Vault archive. There are a few additional steps, as outlined below:

  1. Stop the Enterprise Vault Journal Task, and set the startup of the task to Disabled. Note: The journal mailbox that the task was targeting will now start to grow in size because Enterprise Vault is no longer processing items from it.
  2. Go to the ‘Stage 1 (Sync Data)’ screen.
  3. Locate the container mapping for the journal archive, and select the check box next to it.
  4. From the toolbar, select ‘Enable Stage 2’.
  5. After a few minutes, observe the ‘Stage 2 (Switch User)’ screen and ensure that after a few more minutes the migration is marked as complete.

The Journal Archive has now been moved to a new Vault Store, and a new archive. The final step is to change the journaling process in Enterprise Vault. Usually this is a matter of changing the journal target to be the new archive, and restarting the journal task after setting the task startup back to Automatic.
Note: Depending on the migration being performed, it may also be necessary to reconfigure the Exchange journaling configuration to journal to the new ‘mailbox’.

Enterprise Vault 10.0.4 or later as the Source

Prerequisites

It is essential that the following steps have been completed prior to beginning the migration:

  • All Modules are enabled
  • Appropriate Active Directory Domains is enabled for scanning
  • An Enterprise Vault Environment has been added for migration
  • A Link Database has been created for the source archive
  • Module Mappings are configured for the source Vault Store and also the target Vault Store

Each of the above steps is described in the previous sections of this document.

Map Containers – For the journal archive

The first thing to do when migrating a journal archive to a new vault store is to do a container mapping. This is slightly different than the process followed earlier in the document since we must do a ‘single container mapping’. To setup the mapping, follow these steps:

  1. Navigate to the “Bulk Mapping” page.
  2. Type the beginning of the archive name in the ‘Name’ filter. Click the ‘Apply’ button at the right of the filter row.
  3. Select the checkbox next to the archive, and click ‘Add Mappings’ from the navigation bar.

Note: A short wizard will start, which gathers information relating to the mapping for the archive.

  1. The destination of the migration can then be chosen from the available list and then subsequent pages of the wizard will prompt for further information.

Note: It is recommended that a workflow policy is created that suits the requirements, or the ‘Journal Archive’ workflow is chosen.

Monitoring the Migration

Monitoring the ‘Stage 1’ sync process for a journal archive is the same as with other types of archive migration. A few minutes after setting the policies and enabling migration (see previous section), the container will appear on the ‘Stage 1 (Sync Data)’ screen in the administration console.

Performing Stage 2 and Extra Steps

Migrating a journal archive is slightly different to migrating an ordinary Enterprise Vault archive. There may be some additional steps as outlined below:
Before enabling ‘Stage 2’, the switch, for the test archive, the ‘Stage 1 (Sync Data)’ page should be checked for issues such as failed item-export or item-import.
To enable ‘Stage 2’ for the test archive, perform the following steps:

  1. Navigate to the “Stage 1 (Sync Data)” page.
  2. Select the checkbox next to the test archive, and click on ‘Enable Stage 2’ in the navigation bar.
  3. When the ‘Stage 1 (Sync Data)’ page is refreshed, there should be a green and white check mark in the ‘Stage 2 Enabled’ column.

Stage 2 is the switchover to the target environment. A final synchronization is performed of archived items from the source environment to the target environment, before several additional migration tasks are performed.
The Journal Archive has now been moved to a new Vault Store, and a new archive.
Note: Depending on the migration being performed, it may also be necessary to reconfigure the Exchange journaling configuration to journal to the new ‘mailbox’.

Configuring the Office 365 Environment

Naming Scheme

This determines how mailboxes and accounts will be created, using a token system. The following are tokens which can be used:

  • Archive Name
  • Archive ID
  • Container Mapping ID
  • PST ID
  • PST Number

Note: PST ID and PST Number are applicable if PSTs are the source environment.
In addition to those, alphanumeric characters can be appended or prepended to the name of the mailbox in Office 365.

Usage Location

This is the location relating to license allocation and is required to be chosen from the drop down list.

E-Mail Domain

This should be a valid email domain which will be used to create mailboxes. Eg @something.onmicrosoft.com

Hide from GAL

If enabled the mailbox/user will be hidden from the Global Address List.

Litigation Hold

Litigation hold can be configured, if required, using the Litigation Hold option.

Set Rolling License Count

A specific number of licenses can be used to process the journal splitting mappings. That number should be configured by clicking on ‘Set Rolling License Count’. Licenses will be consumed up to that limit, and will be freed up when stage 2 completes on those mappings.
Note: There is a System Configuration option which can be enabled to migrate the data into Office 365 journal format, if required.

Office 365 Configuration Changes

Journal Splitting Item Count Limit

This determines the maximum number of items which will be in a particular mapping before rolling over to a new mapping.

Journal Splitting Item Size Limit

This determines the maximum size of a mapping before rolling over to a new mapping.

Perform the Journal Mapping

Once the above 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.

Print Friendly, PDF & Email