Archive Shuttle 11.5 - Migration Guide

SourceOne as a source

This section explains the requirements for migrating from SourceOne or EmailXtender to another environment, and then covers the basic steps that should be followed to start such a migration.

Stage 1 - Synch

The first task which has to be performed is the discovery of archives in SourceOne. One or more of these archives are mapped and enabled for migration, Archive Shuttle Core sends a command to collect all needed metadata information from each archive. The results are reported back to Archive Shuttle Core to allow item level tracking and auditing.

The SourceOne module and chosen target environment import module then start to process the items from the archives. This runs continuously in the background until the administrator initiates Stage 2 ('Switch') for the archive.

Stage 2 - Switch

SourceOne to Exchange or Office 365

SourceOne to PST

Requirements

The following is a list of requirements.

Basic steps

The following are the basic steps to start this type of migration.

Determining SourceOne archive owner(s)

Archive Shuttle follows steps below to assign an owner to SourceOne archive:

1. If there is still an Exchange on-premises mailbox, then Archive Shuttle matches it with EmailAddress in dbo.SourceOneArchive table and LegacyExchangeDN in dbo.ExchangeMailbox table and UserSID in dbo.User

2. If there is only an Office 365 mailbox, then Archive Shuttle tries to match owner with SourceOne archive using Address in dbo.UserProxyAddress and EmailAddress in dbo.SourceOneArchive

·dbo.ExchangeMailbox and dbo.UserProxyAddress table are populated during the Azure Directory sync.

·dbo.SourceOneArchive archive is populated during the archive collection.

General considerations

The following general considerations should be taken into account for this type of migration.

·If you need to migrate the primary S1 archive into a primary mailbox, and a secondary S1 archive into a personal archive (in Exchange or Office 365), then two mappings will be required.

·It is recommended to add the following index to the SQL databases relating to S1. It will improve the item collection process: CREATE NONCLUSTERED INDEX [QT_IX_Route_EmailId] ON [dbo].[Route] ([EmailId] ASC) INCLUDE ([MessageID], [RouteMask], [PartitionId])

·It is recommended to add the following index to the SQL databases relating to EmailXtender. It will improve the item collection process: CREATE NONCLUSTERED INDEX [QT_IX_Route_EmailId] ON [dbo].[Route] ([EmailId] ASC) INCLUDE ([MD5HashKey], [TimeStamp])

·Disabling source archives is currently not available as part of a Workflow Policy and will need to be done manually post migration.

·You may find that items exported from these sources are not placed in the folder it originated from. For more information on this, click here.

The following filters are not supported:

·ArchivedDate

·RetentionCategory

·HasLegalHold

Migrating from SourceOne or EmailXTender to a target environment

This section outlines the steps to migrate a single test SourceOne archive to PST.  The same steps can be used to migrate from EmailXtender.

Prerequisites

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

·All Modules are enabled.

·Appropriate Active Directory Domains have been enabled for scanning.

·The PST target links are configured with a specific staging area, and with modules associated to the link.

·The PST Rollover Threshold is configured to an appropriate value.

·The PST Filename policy is defined.

·The Shortcut Process Module must be installed, regardless if shortcuts are being used.

Add a SourceOne Environment

To use SourceOne as a source for migration, a SourceOne Environment needs to be added, and configured as follows:

1.Go to the SourceOne Environment page (Configuration -> SourceOne Environment)

2.Click Add.

3.Enter the details required to connect to the SourceOne Environment

Map Modules to Links

The newly added SourceOne Environment will be added as a Link to the Links page, but modules may still need to be associated with it. This can be achieved as follows:

1.Go to the Links page (Configuration -> Links).

2.Select the SourceOne Link which was created previously.

3.Click Map Modules and check and assign the modules on the link.

Map containers - for the test archive

To migrate a test SourceOne archive to PST file, the source and target containers must be mapped. This can be done as follows:

1.Navigate to the Bulk Mapping page.

2.Change the filter for Type, so it is set to SourceOne. This will show all the discovered SourceOne archives.

3.Locate the archive you wish to use to test the migration, and select it.

4.With the container still selected, click Add Mappings from the navigation bar.

5.On the Target Container Type screen, select PST, and click [Next].

6.On the Choose a format screen, select PST, and then click [Next].

7.On the Choose Target Link screen, choose the appropriate PST link.

8.On the Workflow Policy screen, select the SourceOne to PST option, and click [Next].

9.On the Filter Policy screen, select the Default (No Filter) option, and click ‘Next’.

10.On the Container Mapping Settings screen, select Enabled for both Migration Status and Item Gathering Status, and click on ‘Next’.

11.Review the summary screen before clicking ‘Confirm’.

Review Stage 1 Status

A few minutes after the mapping has been created, the program will instruct the appropriate modules to start the actions defined in the mapping. The progress for this stage of the migration can be reviewed by doing the following:

1.Go to the Stage 1 (Sync Data) 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.Once the source archive is displayed, click Refresh from time to time to show the progress of the export of the archive and the ingesting of the data into the target Archive. Continue to click Refresh until both export and import are 100%.

If further data is added to the source archive, it will be synchronized every 24 hours to the target archive via the connection made with the mapping performed in the previous section. In addition, part of the Stage 2 Workflow is to perform a ‘final synch’. Therefore, it’s not necessary to ensure that export and import has reached 100% before moving on to the next steps.

Validate exported data

If there is a large amount of data to export and import, you can view the progress bars for the Stage 1 (Sync Data) move by clicking Refresh from the navigation bar on the Stage 1 (Sync Data) page of the user interface.

In addition, you can use Windows Explorer to browse the export/import storage area data on the disk.

Also at this time it will be possible to login to Outlook or Outlook Web Access as the test user. The migrated data will be present in the Personal Archive, and can be freely opened and manipulated.

Enable Stage 2 Status

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 then click 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 temporary PST file, before several additional migration tasks are performed.

Review Stage 2 Status

After a few minutes, the progress of the test archive migration will be visible in the Stage 2 Status page, as follows:

1.Navigate to the Stage 2 (Switch User) page.

2.Type the beginning of the archive name in the Name filter. Click the Apply button at the right of the filter row.

Once the source archive is displayed, you can click Refresh from time to time to show the progress of the final stages of the archive migration. By default, since the workflow policy that was selected was PST to Exchange/Office 365 (without archive deletion), the following steps will be performed:

a)Export any remaining items from the PST file

b)Import the remaining items in to the target

Verify data has been migrated

Once all of the Stage 2 operations have been completed the Stage 2 (Sync Data) for the test archive will have a green and white check mark in the Finished column.

In addition, if Outlook or Outlook Web Access is used to access the test mailbox then all of the archived items will be in the Personal Archive, and no Enterprise Vault shortcuts will remain in the source mailbox.

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.