Chat now with support
Chat with Support

Quadrotech Archive Shuttle 10.3 - Migration Guide

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

info

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 is the location relating to license allocation and is required to be chosen from the drop down list.

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 Legal 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 Set Rolling License Count. Licenses will be consumed up to that limit, and will be freed up when stage 2 completes on those mappings.

info

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.

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.

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

info

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.

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.

info

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.

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.

info

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.

info

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

info

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.

info

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.0.4 or Later 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

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.

info

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

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

info

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

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.

info

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.

info

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.

info

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.

info

NOTE: Depending on the migration being performed, it may also be necessary to reconfigure the Exchange journaling configuration to journal to the new ‘mailbox’.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating