1. Home
  2. Archive Shuttle
  3. Archive Shuttle Migration Guides
  1. Home
  2. AS Administration
  3. Archive Shuttle Migration Guides

Archive Shuttle Migration Guides

Contents

Introduction

In the following sections are instructions for migrating from a particular source environment to a particular target environment.

Migrating an archive to Enterprise Vault

This section explains how to migrate a single test archive within Enterprise Vault. For the purposes of this test, the migration takes place between two vault stores in the same Enterprise Vault environment.

Prerequisites

The following steps must be completed before the migration begins:

  • Two or more vault stores must exist in the Enterprise Vault environment.
  • All modules must be enabled.
  • Appropriate Active Directory domains must be enabled for scanning.
  • An Enterprise Vault environment has been added for migration.
  • A link database has been created for the source vault store/archives.
  • Module mappings are configured for the source and the target vault stores. The source vault store needs to be linked to an EV Export module, and the target needs to be linked to an EV import module. In addition, an EV Provisioning Module needs to be linked to the source vault store and to the target vault store.

Each of these steps is described earlier in this document.

Add retention category mappings

The final stage of the setup of the archive migration is to map retention categories between the source and target environments.

Note: This step is only required for Enterprise Vault to Enterprise Vault migrations.

Follow the steps below to achieve this task:

  1. Go to Configuration > EV Retention Mappings.
  1. Click Create Mapping.
  1. Select the values from the drop-down lists, and click Add to add the mapping to the retention category grid.

Retention mappings are managed from this screen.

There is an option to use “Add Intrasite Migration Mappings”, which maps each retention category to itself. This can be used in a situation where archives are to be migrated in the same environment. It simply moves the archives to the new location.

Map Containers – For the test archive

In order to migrate a test archive from one vault store to another, the source and target containers must be mapped. This can be done as follows:

  1. Go to Manage & Operations > Bulk Mapping.
  1. Type the beginning of the archive name in the Container Name filter. Click the button in the far right of the filter row in the Apply Filter column.

Note: If the test archive is not displayed, go back to the Configuration > EV Environment page and click Sync all AD Users. Then, select the vault store where the source archive is located and issue a Run Now for Archive Gathering.

  1. Select the checkbox next to the test archive, and click Add Mappings.

Note: A wizard begins gathering information related to the mapping for the select archive. (Multiple archives can also be selected.)

  1. When you’re prompted to select a target container type, select Enterprise Vault, and then click Next.
  1. When you’re prompted to select a target user, select Same User, and then click Next.
  1. When you’re prompted to select a container strategy, select Create new Containers, and then click Next.
  1. Select the link that corresponds to where the archive is to be migrated, and then click Next.

Note: If the target link drop-down list is empty, then it is likely that an EV Import module has not been correctly associated with the link. Review the Links page.

  1. On the Workflow Policy screen, select Standard Workflow – Within same EV Site (without Archive deletion), and then click Next. You don’t need to select the ownerless workflow policy in this situation; it’s optional.

Note: If a group of users was selected containing a mixture of ownerless and normal containers, this screen gives an administrator the option to specify which workflow to use for the ownerless containers.

  1. For the filter policy, select Default (No Filter), and then click Next.
  2. On the Container Mapping Settings screen, select Enabled for both Migration Status and Item Gathering Status, and then click Next.
  1. If desired, set the mapping’s priority, and then click Next.
  1. Review the summary screen. If everything looks as expected, click Confirm.

Review Stage 1 status

A few minutes after the mapping is created, Archive Shuttle tells the appropriate modules to start the actions defined in the mapping. Review the progress for this stage of the migration using these steps:

  1. Go to Manage & Operations > Stage 1 (Sync Data).
  1. Type the beginning of the archive name in the Name filter, and then click the button in the Apply Filter column, found at the far right of the filter row.
  1. Once the source archive displays, click the Refresh button to see the status of the export of the archive and the ingestion of data into the target archive. Continue to click Refresh until both export and import are complete.

Note: If the data progress bars reach 100% for export, but show no progress for import, the Retention Category mappings have likely not been configured.

If more data is added to the source archive, it’s synchronized to the target archive every 24 hours using the connection made with the mapping you created in the previous section. In addition, part of the Stage 2 workflow is to perform a final sync. 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’s a large amount of data to export and import, and you want to check the progress, click the Refresh button located on the navigation bar on the Stage 1 (Sync Data) page.

In addition, you can use Windows Explorer to browse the staging area data on the disk and view the folder structure.

Also, the Enterprise Vault Admin Console shows that an archive exists in the source Vault Store and that a new archive has been created in the target vault store. It’s also possible to grant a service account access to the target archive and perform searches on it to make sure the data matches the source archive.

Enable Stage 2

Before you enable Stage 2, the switch-over, for the test archive, check the Stage 1 (Sync Data) page for issues like failed item-export or failed item-import.

To enable Stage 2 for the test archive, perform these steps:

  1. Open the Stage 1 (Sync Data) page.
  1. Select the checkbox next to the test archive, and click Enable Stage 2 in the navigation bar.
  1. When you refresh the Stage 1 status, a check mark should display in the Stage 2 Enabled column.

Stage 2 is the “switch-over” to the target environment. A final synchronization of archived items is performed from the source environment to the target environment, before several additional migration tasks are performed.

Review Stage 2 status

After a few minutes, the progress of the test archive migration displays on the Stage 2 page:

  1. Go to the Stage 2 (Switch User) page.
  2. Type the beginning of the archive name in the Container Name filter. Apply the filter by clicking the button in the Apply Filter column, located at the far right of the filter row. Note: If the archive isn’t displayed, wait 1-2 minutes, and then click Refresh in the navigation bar.
  3. Once the source archive displays, click Refresh to see the progress of the final stages of the archive migration. By default, since the workflow policy that was selected was Standard policy (without archive deletion), these steps are performed by Archive Shuttle:
  4. Disable source mailbox from Enterprise Vault archiving.
  5. Rename the source archive.
  6. Collect any remaining items for migration.
  7. Import the remaining items into the target.
  8. Zap the mailbox, removing EV settings.
  9. Assign the new archive to the user.
  10. Enable the mailbox for archiving again.
  11. Rename the target archive.

Update all the existing shortcuts to point to the new archive.

Verify data has been migrated

After all Stage 2 operations are complete, the Stage 2 (Switch User) page for the test archive shows a 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 are accessible via the new archive. Shortcuts to archived items will work and open correctly.

Migrating an archive to Exchange 2010/2013

Complete the steps below to migrate a single test archive within Enterprise Vault to an Exchange 2010/2013 personal archive.

Prerequisites

The steps below must be complete before the migration begins:

  • Enable all Modules.
  • Enable appropriate Active Directory domains for scanning.
  • Add an Enterprise Vault environment for the migration.
  • Create a link database for the source archives.
  • Configure module mappings for the source archives and the target Exchange environment.
  • Run a PowerShell command to allow application impersonation.

Each of these steps is described earlier in this article.

In addition, if you’ll use an Exchange personal archive, rather than an ordinary mailbox for the test migration, the personal archive needs to be pre-created. The personal archive doesn’t need to be created on the same mailbox database as the primary mailbox.

Map containers – For the test archive

To migrate a test archive from Enterprise Vault to Exchange 2010/2013, the source and target containers must be mapped. Follow these steps to do it:

  1. Go to Manage & Operations > Bulk Mapping.
  2. Type the beginning of the archive name in the Container Name filter. Click the button in the Apply Filter row, located at the far right of the filter row. Note: If the test archive doesn’t display, go back to the Configuration > EV Environment page and click Sync all AD Users. Then, select the vault store where the source archive is located and click Run Now.
  3. Select the checkbox next to the test archive(s) and click Add Mappings. A wizard runs, gathering information related to the mapping(s) for the selected archive(s).
  4. When you’re prompted to choose a target container type, select Exchange and click Next.
  5. When you’re prompted to choose the type of migration, select Normal and click Next.
  6. When you’re prompted to choose the target mailbox type, select Secondary (Archive) mailbox. Then, in the second part of the dialog select Skip, and then click Next.
  7. When you’re prompted to choose the target user, select Same User, and click Next.
  8. On the Choose Workflow Policy screen, select the Exchange migration (without archive deletion) option, leave the second drop-down list blank, and then click Next.
  9. When you’re prompted to choose a filter policy, leave the Default (No Filter) option selected, and then click Next.
  10. On the Container Mapping Settings screen, select Enabled for both Migration Status and Item Gathering Status, and then click Next.
  11. Leave the priority blank and click Next.
  12. Review the summary screen, and then click Confirm.

Review Stage 1 status

A few minutes after the mapping is created, appropriate modules start the actions defined in the mapping. The progress of this stage of the migration can be reviewed by following these steps:

  1. Go to the Stage 1 (Sync Data) page.
  2. Type the beginning of the archive name in the Name filter. Click the Apply Filter button at the far right of the filter row.
  3. Once the source archive displays, click Refresh to see the progress of the export of the archive and the ingestion of data into the Exchange personal archive. Continue to click Refresh until both the export and import are complete.

Validate exported data

In addition to checking export/import status (using the steps in the Review Stage 1 status procedure above) you can use Windows Explorer to browse the export/import storage area and data on the disk.

It’s also possible to log in 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.

Note: If the test user previously used the Exchange personal archive feature, it might be difficult to locate the migrated data. Because of this, we recommend that the test user has an empty personal archive before migration.

Enable Stage 2

Before enabling Stage 2 (Switch User) for the test archive, check the Stage 1 Status page for issues like failed item-export or item-import.

Complete these steps to enable Stage 2 (Switch User) for the test archive

  1. Go to the Stage 1 (Sync Data) page.
  2. Select the checkbox next to the test archive, and click Enable Stage 2 in the navigation bar.
  3. When you refresh the Stage 1 (Sync Data) page, 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 of archived items is performed from the source environment to the target environment before several additional migration tasks are performed.

Review Stage 2 status

After a few minutes, view the progress of the test archive migration on the Stage 2 Status page by following these steps:

  1. Go to the Stage 2 (Switch User) page.
  2. Type the beginning of the archive name in the Container Name filter. Click the Apply button located at the far right of the row in the Apply Filter column. Note: If the archive is not displayed, wait one to two minutes and click Refresh in the navigation bar.
  3. Once the source archive displays, click the Refresh button to show the progress of the final stages of the archive migration. By default, since the Exchange migration (without archive deletion) workflow policy was selected, the following steps are performed by Archive Shuttle:
    1. Disable source mailbox from Enterprise Vault archiving.
    2. Rename the source archive.
    3. Collect any remaining items for migration.
    4. Import the remaining items into the target.
    5. Delete any Enterprise Vault shortcuts in the mailbox

Verify data has been migrated

Once all Stage 2 operations are complete, the Stage 2 (Sync Data) for the test archive will have a check mark in the Finished column.

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

Migrating an archive to PST

This section outlines the steps that are necessary in order to complete the migration of a single test archive within Enterprise Vault to a PST file.

Prerequisites

It’s essential that the following steps are complete before the migration begins:

  • 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 archives.
  • Module Mappings is configured for the source archives.

Each of the above steps is described earlier in this article.

In addition, a PST Link needs to be created. This is explained later in this article.

Creating a new PST naming policy

Finalized PST files are named according to a chosen PST naming policy. Policies are managed in Archive Shuttle on the Configuration > Naming Policies page.

The Naming Policies page shows existing policies. It’s used to view, edit, and delete existing policies, and create new policies.

Token Description
*username* Username of the owning user (sAMAccountName)
*firstname* First name of the owning user
*lastname* Last name of the owning user
*fullname* Full name of the owning user
*email* E-mail address of the owning user
*upn* User principal name of the owning user
*pstid* IF of the PST file; continuous integer over all PST files
*pstnumber* Number of PST files; continuous integer per user/mapping
*archivename* Name of the archive
*archiveID* The Enterprise Vault archive ID associated with the archive.

Map Containers – For the test archive

To migrate a test archive from Enterprise Vault to a PST file, the source and target containers must be mapped. To do this, follow these steps:

  1. Go to Manage & Operations > Bulk Mapping.
  2. Type the beginning of the archive name in the Container Name filter. Then, click the Apply button located at the far right of the filter row. Note: If the test archive doesn’t display, go back to the Configuration > EV Environment page and click Sync all AD Users. Then select the vault store where the source archive is located and click Run Now.
  3. Select the checkbox next to the test archive, and click Add Mappings. A brief wizard runs, gathering information relating to the mapping for the selected archive (multiple archives can also be selected).
  4. On the Choose Target Link page, select the name of the PST Link from the drop-down list, and click Next.
  5. On the Workflow Policy page, select Native Import (PST) (without archive deletion), and then click Next. You don’t need to select the ownerless workflow policy in this situation; it’s optional.
  6. On the Filter Policy page, select Default (No Filter), and then click Next.
  7. On the PST Filename Policy page, select the name of a policy from the drop-down list, and click Next.
  8. On the Container Mapping Settings page, select Enabled for both Item Gathering Status and Migration Status, and click Next.
  9. If desired, set the mapping’s priority, and then click Next.
  10. Review the summary page, and then click Confirm.

Review Stage 1 status

A few minutes after the mapping is created, modules begin the actions defined in the mapping. Check this stage’s progress by following these steps:

  1. Go to Manage & Operations > Stage 1 (Sync Data).
  2. Type the beginning of the archive name in the Container Name filter. Click the button located at the far right of the filter row to apply the filter.
  3. Once the source archive displays, click Refresh to see the progress of the export of the archive and the ingestion of the data into a temporary PST file. Continue to click Refresh until both export and import are complete.

Validate exported data

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

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

In the case of PST Migration, in the folder on disk containing the exported data, there will be a further sub-folder containing a temporary PST file. You can copy it to a new location and attach to Outlook in order to review its contents.

Enable Stage 2

Before enabling Stage 2, the switch, for the test archive, check the Stage 1 (Sync Data) page for issues like failed item-export or item-import.

Then, to enable Stage 2 for the test archive, perform the following steps:

  1. Go 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 switch-over 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. Go to the Stage 2 (Switch User) page.
  2. Type the beginning of the archive name in the Name filter. Click Apply at the right of the filter row. Note: If the archive is not displayed, wait 1-2 minutes and then click Refresh.
  3. Once the source archive displays, click Refresh from time to time to see the progress of the final stages of the archive migration. By default, since the Native Import (PST) (without archive deletion) workflow policy was selected, the following steps will be performed by Archive Shuttle:
    1. Disable source mailbox from Enterprise Vault archiving.
    2. Rename the source archive.
    3. Collect any remaining items for migration.
    4. Import the remaining items in to the temporary PST file.
    5. Finalize the data in the temporary PST file.
    6. Move the PST file to the PST Output Path, as defined on the PST Link, using the naming standard defined in the filename policy.
    7. Delete any Enterprise Vault shortcuts in the mailbox.
    8. Change any pending-archive items in the source mailbox back to normal items.
    9. Zap the permissions on the source archive.

Verify data has 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, the PST file can be opened with Outlook from the PST Output Path.

Migrating an Archive to Office 365

This section outlines steps of the migration of a single test archive within Enterprise Vault to an Office 365 mailbox.

Prerequisites

Complete these steps before beginning the migration:

  • Enable all modules.
  • Enable appropriate Active Directory Domains for scanning.
  • Add an Enterprise Vault Environment for the migration.
  • Create a Link Database for the source archives.
  • Configure Module Mappings for the source archives.

Each of the above steps is described earlier in this article.

Note: It is assumed that the mailbox has been moved to Office 365 already and that it is the EV Archive that is to be moved.

Office 365 Global Admin

In addition, it is necessary to configure the Archive Shuttle to Office 365 connection to use credentials that have sufficient privileges. It is recommended to configure multiple accounts with Application Impersonation Rights.

Note: By default, Archive Shuttle will ingest into five containers simultaneously; therefore, it is recommended to have at least five service accounts.

User Principal Name (UPN)

When mailbox information is gathered from Office 365, they are matched against local Active Directory users by using the Primary SMTP Address.

This means that the local Active Directory users must have the same UPN as the Office 365 users, or have the same Primary SMTP Address.

Note: Archive Shuttle does not support automatic matching of mailboxes to more than one set of Active Directory users (for example, matching to both on-prem and cloud users) when the same UPNs are present in both Active Directory instances.

Configure the Office 365 Module

The Office 365 module needs credentials supplying to it in order to be able to connect to Office 365. To provide these credentials, follow the steps below:

  1. Log in to the server or workstation where the Office 365 Module is currently deployed using the account that is used to run the Archive Shuttle Office 365 Service.
  1. Click Start and locate the Credentials Editor, and then click it to launch the editor.
  1. In the small application that launches, click Add and enter the account UPN and password for the account described in the prerequisites section.
  1. Click OK on the UPN/Password dialog.
  1. Click Save in the Credential Editor, and close the application

These credentials will be used by the module when it connects to Office 365.

The final step in configuring the module is to start the Office 365 Module Service using the Windows Service Control Manager.

Note: Additional configuration may be necessary in order to obtain good ingest performance, and/or to work in environments where web/HTTP proxies are used. These are described in the Installation Overview.

Note: Alternatively, you can use OAuth instead of service account credentials. To do this, add the OAuth credentials using the Credential Editor, and also select the Use modern authentication (OAuth) option on the Office 365 Module settings.

In order to migrate an archive to Office 365, an Archive Shuttle Office 365 Link is required. Follow these steps to configured it:

  1. Go to the Links page.
  2. Click Office 365 in the Actions Bar.
  3. Click Create Link.
  4. Give the link a name, for example, O365.
  5. Click Create.

The new link needs to have Archive Shuttle Modules associated with it, and the Staging Area Path needs to match the EV Export Module.

Sync mailbox data

Before you can map a container in the source environment to an Office 365 target, select the Office 365 link on the Links administration page, and click Sync Mailboxes in the Actions Bar.

Map Containers – For the test archive

In order to migrate a test archive from Enterprise Vault to Office 365, the source and target containers must be mapped. This can be done as follows:

  1. Go to the Bulk Mapping page.
  1. Type the beginning of the archive name in the Name filter. Click Apply, located at the right of the filter row.

Note: If the test archive is not displayed, go back to the EV Environment page and click Sync all AD Users, then select the Vault Store where the source archive is located and issue a Run Now for Archive Gathering.

  1. Select the checkbox next to the test archive, and click Add Mappings.

Note: A short wizard runs, gathering information related to the mapping for the select archive. (Multiple archives can also be selected.)

  1. On the Target Container Type screen, select Office 365, and click Next.
  1. Choose whether the migration should be performed to an Office 365 Mailbox or Personal Archive, and click Next.
  1. Select the link to use for this operation, and click Next.
  1. Choose the Workflow Policy for this migration, and click Next.
  1. Choose the Filter Policy for this migration, and click Next.
  1. On the Container Mapping Settings screen, select Enabled for both Migration Status and Item Gathering Status, and click Next.
  1. Review the summary screen before clicking Confirm.

Review Stage 1 status

A few minutes after the mapping is created, Archive Shuttle instructs the appropriate modules to start the actions defined in the mapping. The progress of this stage of the migration can be reviewed as follows:

  1. Go to the Stage 1 (Sync Data) page.
  1. Type the beginning of the archive name in the Name filter. Click Apply at the right of the filter row.
  1. Once the source archive displays, click Refresh from time to time to show the progress of the export of the archive and the ingesting of the data into Office 365. Continue to click Refresh until both export and import reach 100%.

Validate exported data

If there is a large amount of data to export and import, then it will be possible to see the progress bars for the Stage 1 Status 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 view 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 Office 365 mailbox, and can be freely opened and manipulated.

Enable Stage 2

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. Go to the Stage 1 (Sync Data) page.
  1. Select the checkbox next to the test archive, and click Enable Stage 2 in the navigation bar.
  1. When the Stage 1 Status 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.

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. Go to the Stage 2 (Switch User) page.
  1. Type the beginning of the archive name in the Name filter. Click Apply at the right of the filter row.

Note: If the archive is not displayed, wait one to two minutes and click Refresh in the navigation bar.

  1. 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 which was selected was ‘Office 365 (without archive deletion)’, the following steps will be performed by Archive Shuttle:
    1. Rename the source archive
    2. Collect any remaining items for migration
    3. Import the remaining items in to the target
    4. Delete any Enterprise Vault shortcuts in the Office 365 mailbox
    5. Change any archive-pending items back to normal items in the Office 365 mailbox

Verify data has migrated

Once all of the Stage 2 operations have been completed, the ‘Stage 2 (Switch User)’ for the test archive will have a green and white check mark in the ‘Finished’ column.

In addition Outlook or Outlook Web Access can be used to access the Office 365 mailbox to verify that all data from the Enterprise Vault archive is present and accessible.

Migrating from PST to a target environment

This section of the document will outline the steps to migrate a single test PST to an Exchange 2010/2013 Personal Archive.

Note: The steps are largely the same when migrating from source PST files to any supported target environment.

Prerequisites

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

  • All Modules should be enabled
  • Appropriate Active Directory Domains have been enabled for scanning
  • The Exchange target links should be configured with a specific staging area, and with modules associated to the link.

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

To use PST as a source for migration, a PST link needs to be created and configured:

  1. Go to Configuration > Links.
  1. On the PST tab click Create Link.
  1. Give the link a meaningful name (for example, PST Source).
  1. Specify a UNC path, in this case it can be any path, because it will not be used in the case of using PST as a source.
  1. With the link still selected, click on Map Modules on the Link tab.
  1. A Native Export Module should be selected underneath the Source option.
  1. With the link still selected, click Create Database to create a link database.

Scan PST Location(s)

The PST link needs to be configured with one or more source UNC paths to scan for PSTs, so that they can be migrated from. This can be achieved as follows:

  1. Go to Configuration > Links.
  1. Select the PST link that was created in the previous step.
  1. On the PST tab select PST Source.
  1. Click New, which is located in the center of the dialog, and enter a UNC path to scan for PSTs.
  1. If required, multiple paths can be entered.

Note: Clicking Scan after adding a new UNC path for the module is not necessary, it will scan new paths automatically

Map Containers – For the test archive

To migrate a test archive from one vault store to another, the source and target containers must be mapped:

  1. Go to the Bulk Mapping page.
  1. Change the filter for “Type”, so it is set to PST. This will show all the discovered PST files.

Note: The PSTs will show as ownerless, and will display the file path and file name. The number of items in the PST will show as zero at this stage

  1. Locate the PST you wish to use to test the migration, and select it.
  1. Click on ‘Assign Archive User’ and pick an Active Directory user whose mailbox will be the target of the migration.
  1. With the container still selected, click ‘Add Mappings’ from the navigation bar.

Note: A short wizard will start, which gathers information relating to the mapping for the select archive. (Multiple archives can also be selected)

  1. On the ‘Target Container Type’ screen, select ‘Exchange’, and click ‘Next’.
  1. On the ‘Choose target mailbox type’ screen, select ‘Secondary (Archive) mailbox’. In the second part of the dialog select ‘Map to primary mailbox’ if the secondary mailbox does not exist, and then click on ‘Next’.
  1. On the ‘Target User’ screen, select ‘Same User’ and click on ‘Next’
  1. On the ‘Workflow Policy’ screen, select the ‘PST to Exchange/Office365 (without archive deletion)’ option, and click on ‘Next’.
  1. On the ‘Filter Policy’ screen, select the ‘Default (No Filter)’ option, and click ‘Next’.
  1. On the ‘Container Mapping Settings’ screen, select ‘Enabled’ for both Migration Status and Item Gathering Status, and click on ‘Next’.
  1. Review the summary screen before clicking ‘Confirm’.

Note: If the PST is not assigned an owner, it is still possible to use the Manual Mapping screen in Archive Shuttle to perform a migration from PST to a target.

Review Stage 1 Status

A few minutes after the mapping has been created, Archive Shuttle 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.
  1. Type the beginning of the archive name in the ‘Name’ filter. Click on the ‘Apply’ button at the right of the filter row.
  1. 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.

Note: If the test user previously used the Personal Archive feature, it might be difficult to locate the migrated data. Because of this, we recommend that the test user has an empty personal archive before migration.

Enable Stage 2

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 on the ‘Apply’ button at the right of the filter row. Note: If the archive is not displayed, wait one to two minutes and click ‘Refresh’ in the navigation bar
  1. 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 by Archive Shuttle:
    1. Export any remaining items from the PST file
    2. Import the remaining items in to the target

Verify data has 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 from EAS to a target environment

This section of the document will outline the steps which are necessary in order to complete the migration of a single test EAS to Enterprise Vault.

Note: The steps are largely the same when migrating from EAS to any supported target environment.

Prerequisites

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

  • All Modules should be enabled
  • Appropriate Active Directory Domains have been enabled for scanning
  • The Enterprise Vault target links should be configured with a specific staging area, and with modules associated to the link.

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

Add an EAS Environment

In order to use EAS as a source for migration, an EAS Environment needs to be added, and configured as follows:

  1. Go to the EAS Environment page in Archive Shuttle (Configuration -> EAS Environment)
  2. Click Add.
  3. Enter the details required to connect to the EAS Environment.
  4. Go to the System Configuration page for EAS, and enter the URL to be used to connect to the EAS WebServer.

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

  1. Go to Configuration > Links.
  1. Select the EAS Link which was created previously.
  1. Click Map Modules and check and assign the modules on the link.

Map Containers – For the test archive

In order to migrate a test EAS archive to an Enterprise Vault environment, the source and target containers must be mapped. This can be done as follows:

  1. Navigate to the System Configuration page
  2. On the EV Import Module tab, enter the retention category ID to use for the items which will be ingested into Enterprise Vault.
  3. Navigate to the ‘Bulk Mapping’ Page.
  4. Change the filter for “Type”, so it is set to EAS. This will show all the discovered EAS archives.
  5. Locate the archive you wish to use to test the migration, and select it.
  6. With the container still selected, click ‘Add Mappings’ from the navigation bar. Note: A short wizard will start, which gathers information relating to the mapping for the select archive. (Multiple archives can also be selected)
  7. On the ‘Target Container Type’ screen, select ‘Enterprise Vault’, and click ‘Next’.
  8. On the ‘Choose target user type’ screen, select ‘Same User’, and then click on ‘Next’.
  9. On the ‘New or Existing Container’ screen, select ‘Create new Containers’ and click on ‘Next’.
  10. On the ‘Choose Target Link’ screen, choose the appropriate Enterprise Vault target link.
  11. On the ‘Workflow Policy’ screen, select the ‘EAS to Enterprise Vault (without archive deletion)’ option, and click on ‘Next’.
  12. On the ‘Filter Policy’ screen, select the ‘Default (No Filter)’ option, and click ‘Next’.
  13. On the ‘Container Mapping Settings’ screen, select ‘Enabled’ for both Migration Status and Item Gathering Status, and click on ‘Next’.
  14. Review the summary screen before clicking ‘Confirm’.

Review Stage 1 Status

A few minutes after the mapping has been created, Archive Shuttle 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. Navigate to the “Stage 1 (Sync Data)” page.
  2. Type the beginning of the archive name in the ‘Name’ filter. Click on 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%.

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.

Enable Stage 2

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.
  1. Type the beginning of the archive name in the ‘Name’ filter. Click on the ‘Apply’ button at the right of the filter row.

Note: If the archive is not displayed, wait one to two minutes and click ‘Refresh’ in the navigation bar

  1. 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 ‘EAST to Enterprise Vault (without archive deletion)’, the following steps will be performed by Archive Shuttle:
    1. Disable archiving in EAS
    2. Import the remaining items in to the target
    3. Assign the EV archive to the end user
    4. Enable the mailbox for archiving in Enterprise Vault
    5. Rename the target archive (to remove ‘Archive Shuttle
    6. Update all existing EAS shortcuts in the mailbox and convert them to Enterprise Vault shortcuts.

Verify data has 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 from DAM to a target environment

This section of the document will outline the steps which are necessary in order to complete the migration of a single test DAM to PST.

Note: The steps are largely the same when migrating from DAM to any supported target environment.

Prerequisites

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

  • All Modules should be enabled
  • Appropriate Active Directory Domains have been enabled for scanning
  • The PST target links should be configured with a specific staging area, and with modules associated to the link.
  • The PST Rollover Threshold should be configured to an appropriate value.
  • The PST Filename policy should be defined.

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

Add a DAM Environment

In order to use DAM as a source for migration, a DAM Environment needs to be added, and configured as follows:

  1. Go to the DAM Environment page in Archive Shuttle (Configuration -> Dell Archive Manager Environment)
  2. Click on ‘Add’
  3. Enter the details required to connect to the DAM Environment

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

  1. Go to Configuration > Links.
  2. Select the DAM Link which was created previously.
  3. Click on ‘Map Modules’ and check and assign the modules on the link.

Map Containers – For the test archive

In order to migrate a test DAM 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 DAM. This will show all the discovered DAM 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. Note: A short wizard will start, which gathers information relating to the mapping for the select archive. (Multiple archives can also be selected)
  5. On the ‘Target Container Type’ screen, select ‘PST’, and click ‘Next’.
  6. On the ‘Choose a format’ screen, select ‘PST’, and then click on ‘Next’.
  7. On the ‘Choose Target Link’ screen, choose the appropriate PST link.
  8. On the ‘Workflow Policy’ screen, select the ‘Dell Archive Manager to PST)’ option, and click on ‘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, Archive Shuttle 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 on 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%.

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.

Enable Stage 2

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.
    1. Select the checkbox next to the test archive, and then click ‘Enable Stage 2’ in the navigation bar.
  1. 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.
  1. Type the beginning of the archive name in the ‘Name’ filter. Click on the ‘Apply’ button at the right of the filter row.

Note: If the archive is not displayed, wait one to two minutes and click ‘Refresh’ in the navigation bar.

  1. 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 ‘Dell Archive Manager to PST’, the following steps will be performed by Archive Shuttle:
    1. Disable archiving in DAM
    2. Import the remaining items in to the target
    3. Close the PST file
    4. Rename the PST file, according to the file name policy
    5. Delete the shortcuts from the mailbox.

Verify data has 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.

The PST file can that was created can then be attached to Outlook and reviewed to ensure that the data was successfully migrated.

Migrating from Metalogix Archive Manager to a target environment

This section of the document will outline the steps that are necessary to complete the migration of a single test Metalogix to Enterprise Vault.

Note: The steps are largely the same when migrating from Metalogix to any supported target environment.

Prerequisites

It is essential that the following steps have been completed before the migration begins:

  • All Modules are enabled.
  • Appropriate Active Directory Domains have been enabled for scanning.
  • The Metalogix target links should be configured with a specific staging area, and with modules associated to the link.

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

Add a Metalogix Environment

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

  1. Go to the Metalogix Environment page in Archive Shuttle (Configuration > Metalogix Environment).
  2. Click Add.
  3. Enter the details required to connect to the Metalogix environment.
  4. Go to the System Configuration page for Metalogix and enter the URL to be used to connect to the Metalogix WebServer.

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

  1. Go to Configuration > Links.
  1. Select the Metalogix Link you created.
  1. Click Map Modules and check and assign the modules on the link.

Map Containers – For the test archive

To migrate a test Metalogix archive to an Enterprise Vault environment, the source and target containers must be mapped. This can be done as follows:

  1. Navigate to the System Configuration page
  2. On the EV Import Module tab, enter the retention category ID to use for the items which will be ingested into Enterprise Vault.
  3. Open the ‘Bulk Mapping’ Page.
  4. Change the filter for “Type”, so it is set to Metalogix. This will show all the discovered Metalogix archives.
  5. Locate the archive you want to use to test the migration, and select it.
  6. With the container still selected, click ‘Add Mappings’ from the navigation bar. Note: A short wizard will start, which gathers information relating to the mapping for the select archive. (Multiple archives can also be selected)
  7. On the ‘Target Container Type’ screen, select ‘Enterprise Vault’, and click ‘Next’.
  8. On the ‘Choose target user type’ screen, select ‘Same User’, and then click on ‘Next’.
  9. On the ‘New or Existing Container’ screen, select ‘Create new Containers’ and click on ‘Next’.
  10. On the ‘Choose Target Link’ screen, choose the appropriate Enterprise Vault target link.
  11. On the ‘Workflow Policy’ screen, select the ‘Metalogix to EnterpriseVault (without archive deletion)’ option, and click on ‘Next’.
  12. On the ‘Filter Policy’ screen, select the ‘Default (No Filter)’ option, and click ‘Next’.
  13. On the ‘Container Mapping Settings’ screen, select ‘Enabled’ for both Migration Status and Item Gathering Status, and click on ‘Next’.
  14. Review the summary screen before clicking ‘Confirm’.

Review Stage 1 Status

A few minutes after the mapping has been created, Archive Shuttle 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 on 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%.

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.

Enable Stage 2

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. Go 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. Go to the “Stage 2 (Switch User)” page.
  1. Type the beginning of the archive name in the ‘Name’ filter. Click on the ‘Apply’ button at the right of the filter row. Note: If the archive is not displayed, wait one to two minutes and click ‘Refresh’ in the navigation bar
  1. 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 ‘EAST to Enterprise Vault (without archive deletion)’, the following steps will be performed by Archive Shuttle:
    1. Disable archiving in Metalogix
    2. Import the remaining items in to the target
    3. Assign the EV archive to the end user
    4. Enable the mailbox for archiving in Enterprise Vault
    5. Rename the target archive (to remove ‘Archive Shuttle‘)
    6. Update all existing Metalogix shortcuts in the mailbox and convert them to Enterprise Vault shortcuts.

Verify data has 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 from SourceOne or EmailXtender to a target environment

This section of the document will outline the steps which are necessary in order to complete the migration of a single test SourceOne archive to PST. The same steps can be used to migrate from EmailXtender.

Note: The steps are largely the same when migrating from SourceOne to any supported target environment.

Prerequisites

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

  • All Modules should be enabled
  • Appropriate Active Directory Domains have been enabled for scanning
  • The PST target links should be configured with a specific staging area, and with modules associated to the link.
  • The PST Rollover Threshold should be configured to an appropriate value.
  • The PST Filename policy should be defined.

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

Add a SourceOne Environment

In order 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 in Archive Shuttle (Configuration -> SourceOne Environment)
  2. Click on ‘Add’
  3. Enter the details required to connect to the SourceOne Environment

The newly added SourceOne Environment will be added as a Link to the Links page in Archive Shuttle, 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 on ‘Map Modules’ and check and assign the modules on the link.

Map Containers – For the test archive

In order 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. Note: A short wizard will start, which gathers information relating to the mapping for the select archive. (Multiple archives can also be selected)
  5. On the ‘Target Container Type’ screen, select ‘PST’, and click ‘Next’.
  6. On the ‘Choose a format’ screen, select ‘PST’, and then click on ‘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 on ‘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, Archive Shuttle 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. Navigate to the “Stage 1 (Sync Data)” page.
  2. Type the beginning of the archive name in the ‘Name’ filter. Click on 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%.

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.

Enable Stage 2

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. Go to the Stage 2 (Switch User) page.
  1. Type the beginning of the archive name in the ‘Name’ filter. Click on the ‘Apply’ button at the right of the filter row.

Note: If the archive is not displayed, wait one to two minutes and click ‘Refresh’ in the navigation bar.

  1. 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 ‘SourceOne to PST’, the following steps will be performed by Archive Shuttle:
    1. Import the remaining items in to the target
    2. Close the PST file
    3. Rename the PST file, according to the file name policy
    4. Delete the shortcuts from the mailbox.

Verify data has 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.

The PST file can that was created can then be attached to Outlook and reviewed to ensure that the data was successfully migrated.

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 Archive Shuttle targets, as described in the following sections

Migrating to Native Format 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 Archive Shuttle 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 Native Format (PST).

Note: For information relating to migrating journal archives to Office 365, using Virtual Journals, 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 Native Format, or Exchange, navigate to the System Configuration page in the Archive Shuttle 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 Archive Shuttleadministration 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. In Archive Shuttle, 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 Archive Shuttleadministration 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’.

Migrating a Journal Archive to Office 365

Journal Archives in source environments are typically large. Their multiple terabyte nature makes it currently quite hard to migrate the data to Office 365 as there are limits imposed by Microsoft on both the mailbox and personal archive sizes. To be able to migrate a large journal archive to Office 365 Archive Shuttle introduced a concept of a ‘Virtual Journal.

The general process for doing this is:

  1. Define the naming scheme for the target. It is suggested to prefix or postfix names, eg AL-<archivename> or <archivename>-Departed. This makes the data easier to find in the target after the migration has completed.
  2. Define the allowed number of rolling licenses.
  3. Decide on the type of ‘hold’ to place on the migrated data.
  4. Configure the maximum number of items allowed per child container, and maximum size allowed.
  5. Perform the mapping.

In the background what will happen is:

a. Provisioning

  1. A user account will be created according to the naming scheme.
  2. A Personal Archive will be created if it was required in the mapping.
  3. The mailbox/personal archive will be placed on the selected type of hold.
  4. A license will be assigned from the pool.
  5. The data from Office 365 about the ‘user’ will be synchronized into Archive Shuttle

b. Migration

  1. Data will be exported after the provisioning process is done.
  2. Data will be imported soon after it is exported, when a particular child container is full, as determined by the system settings, a new one will be created.

c. Stage 2

  1. The license which was assigned in order to be able to ingest data in to the mailbox (or Personal Archive) will be removed (usually as the last step) and returned to the pool so that another mapping can take that license and complete the provisioning step.

To use the Virtual Journal feature there are a number of steps that need to be performed, as outlined below:

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 virtual journal 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

Virtual Journal Item Count Limit

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

Virtual Journal 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 a virtual journal.

Migrating a Shared Mailbox Archive

This section of the document will outline the steps that are necessary in order to complete the migration of an archive shared amongst a group of users. The migration will be from one Enterprise Vault environment to another.

In Enterprise Vault, this may simply be a regular mailbox archive so that is maintains the structure from the mailbox where the data comes from. The mailbox itself will ultimately have one true owner in Active Directory, but a number of other users and/or groups may also have access to both the mailbox and the archive.

Capture Permissions on the Source

There a number of ways in which the permissions can be shown for an archive, including the following:

    • Open the properties of the archive in the Vault Administration Console, and check the entries on the permissions tab
  • Use a script similar to the one provided on the Symantec Connect web site:

https://vox.veritas.com/t5/Articles/Script-to-know-AD-permission-assigned-on-Archives-Folders/ta-p/806130

Build an EVPM file

From the list of permissions on the source archive an EVPM file should be built. There are details about the way to use EVPM in the Enterprise Vault Utilities Guide. At a high level the steps are:

    • Directory section should contain information about the Enterprise Vault Directory computer and Enterprise Vault site name.
    • A section should be added called ‘ArchivePermissions’
    • The Archive Name property should be added to this section with the name of the archive.
  • The Grant Access property should be added to this section with a list of people to grant access to the archive. This should be listed one per line.

Perform the Migration

The migration of the archive/container can then be performed. Particular care should be taken in relation to migrating these types of archives/containers because the migration has an impact on a number of people.

Apply the EVPM file

Following the successful migration of the Shared Mailbox / Archive, the EVPM file that was created previously should be run to grant permissions on to the target/new archive.

Migrating Leavers to Office 365

Archive Shuttle can manage a pool of licenses to provision and migrate data to Office 365 mailboxes or archives that are ownerless. It can even treat an archive as though it is ownerless, and migrate it using this process, even if an owner shows in the user interface.

The general process for doing this is:

  1. Define the naming scheme for the target. It is suggested to prefix or postfix names, ex. AL-<archivename> or <archivename>-Departed. This makes the data easier to find in the target after the migration has completed.
  2. Define the allowed number of rolling licenses.
  3. Decide on the type of ‘hold’ to place on the migrated data.
  4. Perform the mappings.

In the background what will happen is:

a. Provisioning

  1. A user account is created according to the naming scheme.
  2. A Personal Archive is created if it was required in the mapping.
  3. The mailbox/personal archive is placed on the selected type of hold.
  4. A license is assigned from the pool.
  5. The data from Office 365 about the ‘user’ is synchronized into Archive Shuttle.

b. Migration

  1. Data is exported after the provisioning process is done.
  2. Data is imported soon after it’s exported.

c. Stage 2

  1. The familiar parts of the workflow still occur, such as renaming the source archive, doing a final delta, and so on.
  2. The license that was assigned in order to be able to ingest data into the mailbox (or Personal Archive) is removed (usually as the last step) and returned to the pool so that another mapping can take that license and complete the provisioning step.

How to set this up is described below.

Requirements

The normal Office 365 migration requirements are necessary (see the earlier section). In addition, note that Azure management tools are required. These can be downloaded from: https://msdn.microsoft.com/en-us/library/azure/jj151815.aspx

If these components are not installed, the normal Office 365 migrations will still be successful, but processing of leavers will not be successful. They can be added at any time during the migration; it is not necessary to reinstall or modify the Office 365 module following their installation.

Configuring the Office 365 Environment

Naming Scheme

This determines how mailboxes and accounts will be created, using a token system. The following tokens 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 related to license allocation and is required to be chosen from the drop-down list.

E-Mail Domain

This should be a valid email domain that will be used to create mailboxes. Ex. @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.

Load Licenses

Licenses can be loaded by clicking the Load Licenses button on the Archive Shuttle ribbon. These will also be loaded after adding a new Office 365 link.

Set Rolling License Count

A specific number of licenses can be used to process leavers. That number should be configured by clicking Set Rolling License Count. Licenses will be consumed up to that limit to migrate users, and will be freed up when Stage 2 completes on those users. When mailboxes are created, personal archives are also created.

Perform the Migration

The migration of the archive/container can then be performed. The process of mapping the users is the same as with a normal Office 365 migration, however, there is an additional option in the Mapping Wizard where you can select to use Office 365 Leavers, and you should select an Office 365 Leavers Workflow.

A container can be processed as a leaver if one or more of the following is satisfied:

  • It is ownerless in the user interface
  • The Active Directory account is disabled
  • The Active Directory account is deleted and exists in the Active Directory Dumpster. Note: The account running the AD Collector module must have permissions to read the contents of the dumpster.

Note: Archives will be exported, but only the configured number of rolling licensed users will ingest data into the target.

Stage 2

The Stage 2 workflow (Office365RemoveUser) for Office 365 leavers functions in a similar manner to the normal Office 365 workflows. There is an additional step in the workflow that handles the removal of licenses. Once the license has been removed, if there are additional users that require migration using the leavers process then these will begin migration.

Handling users who leave during a migration

During a migration, if Archive Shuttle detects that a mailbox is no longer present, the user is marked IsDeleted.

Then, you can select the user and select the Enable to Recreate button on the Bulk Mapping page. This enables the leaver mailbox to be created. The user’s data then gets ingested into the leaver mailbox, as described above.

Or, you can automate the process by selecting the option to Enable auto-recreate deleted O365 Users as Leavers located on the Office 365 Module page.

Print Friendly, PDF & Email
Updated on June 9, 2020

Was this article helpful?

Related Articles

Leave a Comment