In some environments, it might be necessary to reduce the load generated on an Enterprise Vault server while performing a migration with Archive Shuttle. This article explains some of the options available to do that.
There are essentially two ways that a load can be reduced on an Enterprise Vault Server:
1) Module scheduling
Each module within Archive Shuttle can have a custom schedule applied to it. So, if in a customer environment, the load needs to be reduced on one or more Enterprise Vault servers during the day, the export (or import) modules for those servers can be selected on the Modules page and a custom schedule can be defined.
Note: When a schedule ends, the module will get no new work, but will continue with the work it is currently processing. In other words, when the schedule ends, work will not stop immediately.
2) Module parallelism
The System Configuration area of Archive Shuttle allows module types to be controlled, in relation to their parallelism. This affects all modules of that particular type. There are two types of parallelism for most modules:
- How ‘wide’ they go, which is the mailbox/archive parallelism.
- How ‘deep’ they go, which is the item-level parallelism.
Changing these values and monitoring performance over a period of time allows the load to be gradually changed on the servers in the environment.