LibraCyber Email Archiver uses volume to store archived emails and information about folder structure, perform import and export jobs, store backups and logs.
For each volume is always possible to retrieve the files list, edit the volume configuration or delete the volume.
Volume destination use
Six different destination uses are available for LibraCyber Email Archiver volumes: data, import, export, backup and log.
Data
Date volumes are used to store archived emails.
The archived emails are stored in compressed zip archives. The Archiver creates a new zip every 4000 emails or at the end of the day.
The Archiver stores the new zip files on all the available active volumes. If you add a new volume later and you want to copy all the files from the old volume to the new one, you can run a migration (duplication job, see below). Adding storage redundancy of all archived emails can be done by simply configuring multiple active data volumes for the specific tenant.
Migration job
The content of a data volume can be migrated to another data volume configured on the same Archiver tenant.
When running a migration you have to configure the destination volume and the migration type. The type can be:
- Migration: all files are moved to the destination volume and then deleted from the source volume
- Duplication: all files are copied to the destination volume
Reindex
The LibraCyber Email Archiver allows to reindex all the zip files stored on a data volume.
A reindex can be useful when the indexing engine of the appliance suffered serious problems and you have to reindex all the archived emails.
When running a reindex you have to configure a timeframe and an execution disk, which is a local disk used to temporary store the zip files to be reindexed and to extract them. The space on the execution disk is completely freed up at the end of the process.
Lastly, a priority can be configured. Available priority are Normal, High and Urgent. When configuring a priority higher than Normal, the Archiver reindexes multiple zip files concurrently, based on the appliance resources.
Configuration
When configuring a data volume you have to provide a name (which is only a descriptive label), a priority, a retention time and you have to decide whether the volume should be active or not.
The priority is used when fetching the zip files from the volumes, for example when a user wants to consult an email. When a zip file is stored on multiple volumes, the volume with the highest priority is used to fetch the file. The maximum available priority possible is 1. The priority is very useful if you want to configure a local volume (very fast) and a remote volume (slower). In this case you can set priority 1 on the local volume and priority 2 on the remote volume, so that the Archiver will always use the faster volume first.
With the retention time is possible to decide the time the volume should keep the files stored on. All the elements older than the specified retention time will be deleted. The default retention time is Forever, meaning that the volume content will never be deleted.
Import
Import volumes can be used to import on the LibraCyber Email Archiver a set of archive containing emails. For additional information you can consult the Import Batch page.
When configuring an import volume you can browse it to see its content.
Export
Export volumes can be used to export emails from the LibraCyber Email Archiver.
The Archiver allows to browse the content of the export volume, so you can for example directly download the exported emails when the export job completes.
Backup
Backup volumes can be used to store the backup of the configurations of the LibraCyber Email Archiver.
Log
Log volumes can be used to permanently store all the logs produced by the LibraCyber Email Archiver.
Volume types and configuration
A lot of different volume types are supported. The configuration varies, but all the volume type can be used for all the destination uses described before.
When configuring a volume, a descriptive name and the destination use are always required. Before saving a new volume, or updating an existing one, a validation is always required. The Validate configuration button tries to write a test file on the volume and to read it.
LibraCyber Cloud
For all the Archivers in the LibraCyber Cloud, the volumes configuration is done automatically when configuring a new tenant.
Each Archiver in the LibraCyber Cloud is provided with some hidden configuration files about volume, which are used to create data and folder structure volumes during the tenant creation phase. We offer data redundancy, meaning that data are replicated and stored to 2 different volumes in 2 different geographic location.
It's also possible to create new volumes using the LibraCyber volume types.
For LibraCyber volumes no additional configuration is required.
Other types and configuration
The LibraCyber Email Archiver offers several type of volumes.
Local
Created on a local appliance disk. The only configuration required is the mail folder path.
Remote
Remote volumes (folder shared from any SAMBA/CIFS based storage). You need to enter the CIFS hostname, the remote share and the username/password combination.
FTP
You need to specify the protocol (FTP or FTPS), the hostname/port, the root folder and the username/password.
S3
You need to specify the credentials and a prefix. The Archiver will use only the <bucket>/<prefix> subfolder.
S3 compatible
Any S3 API-compatible storage is supported. You only need to specify the object storage provider hostname. You'll also have a verify certificate flag to disable the certificate validation.
Wasabi
The configuration is the same as S3. If your region is not available in the dropdown, fallback to the s3 compatible object storage support.
Digital Ocean
The configuration is the same as S3, if your region is not available, fallback to the S3 compatible object storage support.
Scaleway
The configuration is the same as S3. If your region is not available fallback to the S3 compatible object storage support.
UKCloud
The configuration is the same as S3. If your region is not available fallback to the S3 compatible object storage support.
Azure
Azure container blob storage support. You need to enter the account name, the account key and the container name. You find the configuration values when you create the key in the azure web interface.
Google cloud storage support. You need to enter the project ID, the bucket name and the keyfile configuration.
Rackspace
You need to enter the endpoint region, the subregion, the object storage service name and the username/password combination.
OVH
You need to enter the SWIFT authentication URL, the region, the userid/password combination and the project id. If your region is not available fallback to the openstack storage support.
SWIFT (openstack)
You need to enter the SWIFT authentication URL, the region, the userid/password combination and the project id.
Backblaze
You need to enter the key, the bucket, the secret, the endpoint (select from the dropdown) and the prefix.