With LibraCyber Email Archiver you can export all the emails (or only a subset) to any remote export volume. The supported export formats are eml, zip and pst.
How to run an export job
An export job can be configured in five steps.
Mail source
In the first step you have to configure the set of emails you want to export. The available options are:
- export all emails from a specific tenant
- export all the emails assigned to a specific user
- export all the emails matching a saved search
In any case, an optional extra filter based on Date from and Date to can be configured. When exporting emails belonging to a specific user, it's possible to export emails of a specific mailbox folder only.
Volume destination
In the second step you have to configure the location where you want to upload the exported files. To run an export job you need to configure an export volume. For additional information about volumes you can consult this page.
Archive format
The LibraCyber Email Archiver support 3 format:
- Raw: the exported emails will be stored as single EML files
- Zip: the exported emails will be stored as compressed zip archives containing EMLs. The size of the zip files can be configured and an optional zip password can be configured, too.
- PST: the exported emails will be stored within PST archives of configurable size.
Security Options
You can choose between security options included in the license (if not available you may need to upgrade your license)
Export data
In the last step you can review the export job configuration and eventually start the export.
When the export starts, a new job will appear in the jobs list.
By opening the details of the job you can monitor the job progress, view the log and browse the export volume to download the exported files.
About performance and limitations
Running export jobs are limited to one per tenant. You may launch more exports at once but keep in mind they will be processed one after another instead of all at once.
The performance of the export process depends on several factors, mainly related to storage and communication speed.
The engine requires disk space equal to five times the maximum export file size you choose. For example, if you export ZIP files of 5 GB each, the engine must have at least 25 GB of free disk space available. If the available disk space on the engine is insufficient, the export process will fail before completion. The system does not automatically resume from partial exports, so make sure adequate space is available before starting.
Exports can still be performed even if the Archiver license has expired.
The speed of the export process is primarily determined by the communication speed with the storage volumes. For every single email that needs to be exported, the system must download the entire ZIP archive containing that message from the remote volume, which can significantly impact performance. To ensure optimal performance, exports should be run over a stable, high-bandwidth connection to the archive volumes. Running exports on a machine connected through slow or unreliable network links can significantly increase processing time.
Additionally, when converting from shared archives to separate per-user archives, the operation involves extensive data movement. This transformation requires additional processing time and resources compared to standard export operations.