TrilioVault has four main software components:
- 1.TrilioVault ships as a QCOW2 image. User can instantiate one or more VMs from the QCOW2 image on a standalone KVM boxes.
- 2.TrilioVault API is a python module that is an extension to nova api service. This module is installed on all OpenStack controller nodes
- 3.TrilioVault Datamover is a python module that is installed on every OpenStack compute nodes
- 4.TrilioVault horizon plugin is installed as an add on to horizon servers. This module is installed on every server that runs horizon service.
The TrilioVault Appliance gets delivered as a qcow2 image, which gets attached to a virtual machine.
Trilio supports KVM-based hypervisors on x86 architectures, with the following properties:
The recommended size of the VM for the TrilioVault Appliance is:
The qcow2 image itself defines the 40GB disk size of the VM.
In addition to the TrilioVault Appliance does TrilioVault contain components, which are installed directly into the Openstack itself.
Additionally, it is necessary to have the
nfs-commonpackages installed on the compute nodes in case of using the NFS protocol for the backup target.
Since TrilioVault for OpenStack 4.2 is TVO capable of providing encrypted backups
The TrilioVault for OpenStack solution is leveraging the OpenStack Barbican service to provide encryption capabilities for its backups.
To be precise, TVO is using secrets provided by Barbican to encrypt and decrypt backups. Barbican is therefore required to utilize this feature.