Sometimes it might be required to move an Archive Shuttle staging area. This article explains the steps which are necessary in order to perform this.
For the purpose of this article we will assume that we have:
– 1 x Enterprise Vault export module running on a source link
– 1 x Office 365 module running on a target link
If there are more modules and more links sharing the same staging area the same process can be followed. Likewise, if other sources are used, and other targets, the same principles apply.
1/ Disable the Enterprise Vault export module, from the Modules page in Archive Shuttle. This will prevent new work being received by the module.
2/ Restart the Enterprise Vault export module, from the Modules page in Archive Shuttle. This will flush out any current work, and send results back to the Core.
3/ Disable the Office 365 module.
4/ Restart the Office 365 module.
5/ Monitor the export and ingest module log files to ensure that they are not exporting or ingesting any data, and that the old data is cleared. You may performance statistics and Items per second.
INFO| OnPerformanceTimerElapsedImpl|Last 1 minute(s) statistics: Count:  | Items/s: [0.00] | kb/s:  | ACPU:  | MaxCPU:  | MinCPU:  | TSize: [0 kb] | ASize: [0 kb] | MaxSize: [0 kb] | | MinSize (kb):  | ATime: [0 ms] | MaxTime: [0 ms] | MinTime: [0 ms] | Processor Core Count:  | Logical Processor Count: 
6/ Create / Obtain the path to the new location to be used for the staging area. Ensure that this area is not being scanned by antivirus products as this will impact performance and may cause other problems during migration.
7/ Go to the Links Page in Archive Shuttle
8/ Locate the link for the export module, and change the staging area path to the new path
9/ Locate the link for the ingest module, and change the staging area path to the new path
10/ Using Windows Explorer copy all of the folders, and all of the data from the old location to the new location
11/ Remove the network share for the original staging area. This will ensure that the new location is being used.
12/ Verify that the new location is being checked in the export module log file as shown in step 5.
13/ Change the System Configuration under ‘General’ called: ‘Do not re-export on file not found’, set it to enabled. Save the changes. This will mean that if the import module can not find the items it requires, it won’t automatically circle the items back around to be re-exported.
14/ Enable the export module, from the Modules page in Archive Shuttle
15/ Verify that the export starts and does not report any errors when writing to the new staging area.
16/ Enable the ingest module, from the Modules page in Archive Shuttle
17/ Verify that the ingest starts, and that items are processed without ‘file not found’ errors.
18/ Change the System Configuration option called ‘Do not re-export on file not found’, back to the previous setting.
Note: This procedure has been tested to work on migrations from Enterprise Vault to Office 365. Migrations involving the PST Export Module, or the Native Format Import module has not been tested at this time.