Journal envelope processing
Prior to Enterprise Vault 10.0.3 journal envelope information was not returned by the Enterprise Vault API. In versions of Enterprise Vault prior to 10.0.3 a process called Envelope Reconstruction is used to rebuild a journal message, where the API-retrieved item can be added, thus giving the entire P1 & P2 message.
Envelope Reconstruction does have a performance impact but is essential for maintaining data integrity and Chain of Custody for journal archive migrations.
In testing the performance impact it was observed that if extract performance was N with an Enterprise Vault 9.0.4 server doing the journal extract (and envelope reconstruction) and that machine was upgraded to 10.0.4, the extract performance would be between 4x and 6x faster than N.
Journal archive folder split settings
When migrating a large source journal archive into a target, you might want to implement and use Folder Splitting functionality in Archive Shuttle, as well as archive splitting. This article explains why.
When migrating from a source archiving system, such as Enterprise Vault, to a new target archiving system, such as Enterprise Vault, there is usually no need to split the source archive in terms of the archive itself, or into new folders (and subfolders).
However, if the migration is to Exchange or Office 365, then it is often desirable for several reasons:
·Office 365 and Exchange have limits on the number of items that can be stored in individual folders.
·Performance in relation to viewing folders that contain millions of items is poor when using Outlook-type clients (MAPI based).
·Mailbox or Personal Archive size limits on the target may prevent a large journal archive being ingestable into a single target container.
For these reasons, splitting at the folder level (which is a configuration of the Enterprise Vault Collector module) is desirable and easy to do. Splitting at the archive level by querying Enterprise Vault and counting the number and size of items in the journal archive per day, per week, per two weeks, or per month. Once a suitable splitting range has been defined, filters based on a date can be implemented in Archive Shuttle, and the source archive can be mapped multiple times to different target archives with different filters.
User Interface
When migrating a journal archive, using the Archive Shuttle folder splitting feature is recommended since many target environments have limits on the number of items that can be in a single folder.
These settings can be found on the Configuration > General System Settings page.
The settings are:
·Journal Split Base Folder Name: This is the name of the top-level folder that will be split when items are ingested into the target environment.
·Journal Split Threshold: This is the number of items that should be placed in each folder before a new folder is created.
The settings above can be applied only for Enterprise Vault and SourceOne sources.
Other sources (like EAS, DAM/QAM, and PST) are not supported. This is because they are unable to recognize the journal archive as a specialized container and are treated like a normal archive. For EAS, DAM/QAM, and PST sources, the large folder setting named Split threshold large folders (except journal / folderless) can be applied on their journal archive.
EV collector journal collection logs
Occasionally, it may be necessary to check the EV Collector log files if there are any issues present. With large journal archives, the collection can take some time, and it might be important to check for collection issues.
First, Archive Shuttle will need to find and open the log files. They are stored on:
a) Machine where are the modules installed (ie: C:\Program Files (x86)\QUADROtech\Logs), in many cases it is the Source EV server. The log file name is AS_EVCollector_Log.txt
b) Machine where is core installed (ie: C:\Program Files\QUADROtech\Logs). You will find there two different log files for EV collector, first is the Client (Module) log file with name ArchiveShuttle.WebServicesLog.HOSTNAME.EVCollector.Client.txt, and the second one is the core log ArchiveShuttle.WebServicesLog.HOSTNAME.EVCollector.txt
Second, the log level may need to be changed to TRACE to collect detailed information.
Alternate mailbox support for discovered addresses associated with active users
In a Journal Transformation migration you might want to migrate active user content into inactive alternate mailboxes. This may simplify the migration and reduce project complexity. You may also want to do this if active users recently departed the organization or re-join after leaving.
In the Bulk Mapping wizard, when you select the Journal Transformation options there is an option called Use alternate mailboxes:
If the option is enabled all collected Journal Transformation users will be treated as leavers after consolidation. This means that the users will be managed from the Journal Transformation Leavers Management page in the user interface.