Every migration which is executed by Journal Commander is different. This means that tuning each migration is also different. However, there a number of good practices which should be considered, and we’ll cover them in this article.

Scheduling module operation

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

 

It is also possible to schedule different aspects of parallelism for different times of the day, rather than just having the modules operate in an off/on manner.

Tuning module parallelism

Each of the modules used in a 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 Core (approximately once per minute)

For reference:
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, Enterprise Vault 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.

 

It is usually recommended to go wide, not deep. This means that you should set the container parallelism to a larger number, and the item parallelism to a lower number.

Enterprise Vault Ingest specific guidance

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

 

It is also possible to configure the Native Format Link to use a different location for the temporary PST files rather than the staging area. This is recommended in order to lessen the space requirements on the staging area.

Office 365 module specific tuning

The size of a batch, and the number of items in a batch can be tuned in a migration to Office 365. This is usually performed by carefully reviewing the log files from the module. If it is observed that there are batches full in terms of space, but not full in terms of the number of items in a batch, then that might indicate that the batch size can be increased. Likewise if a batch is seen to be full in terms of the number of items, but not space, then the number of items in a batch could be increased.

Small increases should be performed, and the effects of the change observed, before making more or large changes.

Print Friendly, PDF & Email