Archive Shuttle 11.0 - Migration Guide

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.

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.

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.

Pre-Enterprise Vault 10.0.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

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

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 Archive Shuttle 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.

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

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

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

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.

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

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.