Tuning a Migration
There are many aspects of a migration that can be tuned with Archive Shuttle, some of these are manual tuning mechanisms, others can be automatic if required.
Scheduling Module Operation
Each Archive Shuttle module can be supplied with a specific schedule. For example, if extraction is allowed only during the evening, so as to lessen the load on the source environment, the export modules can be configured to have an evening-only schedule.
Configuring schedules should be done with careful consideration of the impact on the space requirements on the Staging Area. If exports are occurring all night long, but ingests are not scheduled, the staging area may fill up rapidly.
Tuning Module Parallelism
Each of the modules used in an Archive Shuttle migration operates on a number of containers in parallel and within that a number of items in parallel. The defaults for each module have been chosen following testing in many different environments. They can be adjusted to higher or lower values in the System Configuration. The changes made will take effect the next time the module checks in with the Archive Shuttle Core (approximately once per minute)
Container level parallelism
For example, Office 365 Mailbox Parallelism. This is the number of containers that will be operated on simultaneously by the module
Item level parallelism
For example, EXC Import Item Parallelism. This is the number of items that will be operated on simultaneously per container.
When changing the parallelism, it is advised to make changes in small steps and then observe the impact that this has had on migration performance.
EV Ingest Specific Tuning
An option in the System Configuration allows the EV Import Module to pause if Enterprise Vault is in a scheduled archiving window. Pausing the ingestion during this time lessens the load on the target environment.
In addition, backup mode is checked per target Vault Store every 5 minutes.
When ingesting data the EV Import module will only send data to a Vault Store that is not in backup mode.
Finally, the number of items that are not yet marked as indexed in the target environment is captured per Vault Store once per minute. This is displayed on the System Health page in the Archive Shuttle Admin Interface.
A large index backlog might indicate that the target environment has a problem relating to indexing is indexing slowly
Native Format Import Specific Tuning
An option in the System Configuration allows the Native Format Import module to rename (i.e., move) temporary PST files from the Staging Area to the PST Output Path during Stage 1. Normally, the finalization of PSTs is not performed until Stage 2 is executed for a container mapping, but this can lead to increased pressure for storage requirements on the Staging Area.
Enabling the option in the System Configuration can mean that this pressure is reduced because completed PST files are moved out of the Staging Area and placed in their final location.
Office 365 Specific Tuning
Additional throughput can be achieved by the Office 365 module by setting up and configuring additional service accounts that have application impersonation rights within Office 365. These accounts can then be added to the credentials editor, and the Office 365 module will use them for ingesting data in a round-robin fashion.
More information on configuring multiple service accounts is provided earlier in this guide
The Exchange and Office 365 modules both utilize an intelligent batching mechanism which groups together items based on size, folder and whether the item has an attachment or not.
This can be disabled on a per-module basis, if required.