Configuring Archive Shuttle

This section outlines the basic steps required to configure Archive Shuttle. This is applicable for most archive migration projects. The user interface and other components of Archive Shuttle are explained in subsequent sections. We recommend reading each section before performing the post-installation configuration.

Initial Archive Shuttle setup

After Archive Shuttle has been installed, the following five tasks need to be performed before you start migrating archives:

  • Configure module schedules.
  • Enable Active Directory domains.
  • Add Enterprise Vault environment(s), if Enterprise Vault is the source or target environment.
  • Add link databases.
  • Configure module mappings.

These tasks are explained below.

Configure module schedules

During Archive Shuttle installation, the core product, databases, and a number of modules will have been deployed in the environment in order to fulfill migration requirements. During the installation of the modules, each module is enabled. If modules are not enabled, they will not receive any work from the Archive Shuttle Core.
In order to check that all appropriate modules are enabled and operational, follow these steps:

  1. From the Archive Shuttle web interface, click Configuration > AS Modules in the navigation bar.
  2. Review the list of modules:
    • Ensure all required modules are present. For more information see the Installation Overview, as well as the Planning Guide, which will help you validate this part of the migration.
    • Ensure that the computer name, domain name, and version are as expected.
  1. Verify that all modules are reported appropriately and that none of the modules have a red background. If they do, there is a communication problem between the module and the Archive Shuttle Core.

All of the modules are configured to run continuously by default. If this doesn’t meet your requirements for the migration, modules can be individually scheduled to more suitable times using the Set Schedule button on the AS Modules page. This is described later in this guide.

Enable Active Directory domains

A few minutes after the Active Directory Collector Module is enabled, a list of domains where the Active Directory Collector Module is running become visible on the Configuration > Active Directory page.
By default, all domains are discovered, but won’t be scanned for user accounts. In order to enable one or more domains to be scanned, follow these steps:

  1. From the Archive Shuttle web interface, click Configuration > Active Directory in the navigation bar.
  2. Review the list of domains.
  3. Select the check box next to one or more domains.
  4. Click Enable in the navigation bar.
  5. Make sure the Scan Domain column shows a check mark.

Add Enterprise Vault environment(s)

Note: Skip this step if Enterprise Vault is not the source or target of a migration.
The next step to perform in the migration workflow is to add Enterprise Vault environment(s). This is performed from the Configuration > EV Environment page. This page also displays environments that are currently configured.
If the migration is between two Enterprise Vault directory databases, then this page is used to enter details for both directory databases. If the migration is between Enterprise Vault and an external system, such as Microsoft Exchange or Office 365, then only one Enterprise Vault Directory database is added. Likewise, if the migration is between two Enterprise Vault sites within the same Enterprise Vault directory, only one entry is listed on this page.
In order to add an Enterprise Vault environment, follow these steps:

  1. From the Archive Shuttle web interface, click Configuration > EV Environment.
  2. Click Add to add an Enterprise Vault directory.
  3. Enter the required information (for example, the fully qualified domain name and instance name, if it’s not the default instance).
  4. Click Add/Update to apply the changes to the Archive Shuttle database.

Once you specify required EV Directory databases, the Enterprise Vault Collector Module gathers and displays information about the environment. These are then displayed in the EV Environment page after a few minutes.

Tip: Click Refresh in the navigation bar to reload the list of vault stores.

Enable vault stores

Enable archive collection for each vault store that you’ll use in the migration by following these steps:

  1. From the Archive Shuttle web interface, click Configuration > EV Environment in the navigation bar.
  2. Select the checkbox next to each vault store.
  3. In the navigation bar, click Enable.
  4. Verify that the Archive Collection Enabled column now contains a check mark.

Add link databases

Once archive collection is enabled, the next step in the migration is to add link databases for each of the vault stores. A link database is needed for each link in the source environment.
The Configuration > Links page may already contain some links that were collected from the Active Directory Collector Module (the Exchange databases) and from the Enterprise Vault Collector Module (the Vault Stores, as a result of adding each Enterprise Vault environment). These links are created automatically. You must manually create other links, for example, links to Office 365 and PST. To create a link database:

  1. Open the Configuration > Links page.
  2. Select the tab of the type of link database you’re creating (for example, Office 365), and then click Create Link.
  3. Follow the prompts to create the link.

After a link database is created, check the EV Environment page again to review the progress of the archive and item gathering stages.

Note: The number of archives and size of data will not be populated on the EV Environment page until the module linkage is added, but the vault stores will display.

Configure module mappings

The next stage of the configuration involves mapping modules to the Links in the migration project. To do it, follow these steps:

  1. Go to Configuration > Links.
  2. Select the check box next to a vault store/Exchange database/source link.
  3. Click Map Modules in the navigation bar.
  4. From the pop-up window, select appropriate modules from the drop-down lists, and then click Save.

Edit module mappings

Module mappings can be modified by following these steps:

  1. Go to Configuration > Links.
  2. Select the check box next to a vault store/Exchange database.
  3. Click Map Modules.
  4. Make desired changes to the current mapping for this link, and then click Save.

Shortly after module mappings have been added, the appropriate modules perform their tasks and the Number of Containers column updates to show the number of containers in the link.
For the modules that are performing export and import functions, it’s also important to set the staging area path. The corresponding modules need to be paired up to facilitate the flow of archived data. For example, the EV Export module path should correspond to the Exchange import path if the migration is needed to flow in that direction.

Setting up the staging area path

To configure the staging area path:

  1. Go to the Configuration > Links page.
  2. Select the checkbox next to a vault store/Exchange database/source link.
  3. Click Path and follow the prompts.

Repeat this step for each export and each import module. For the second and subsequent paths you define, the Staging Area Path is pre-populated with the path that was previously used. This makes it possible to quickly configure many modules with the same storage location.
The current export/import path and module mappings can be viewed on the Links page. Make sure all links are correctly defined with the appropriate export/import path before proceeding with the migration of any archived data.
It’s also possible to configure the Default Staging Area Path that all modules and links will use unless the setting is overridden on an individual link.

Validating the setup

Once the stages above have been performed and all necessary setup and configuration steps are complete, the archive migration is ready to begin.
At this point, a collection of links have been defined and mapped to modules that perform tasks on those links. The source and target environments have been defined within Archive Shuttle and all of the Archive Shuttle Modules are enabled and set to an appropriate schedule. Finally, the Enterprise Vault retention categories have been mapped according to the migration needs.

Note: Before proceeding with any migration of archived data, confirm that each stage has been performed.

Depending on the migration, additional steps may be required. These are described later in this guide.

Print Friendly, PDF & Email