TrilioVault for RHV Architecture
Last updated
Was this helpful?
Last updated
Was this helpful?
TrilioVault is following modern principles to provide a native, userfriendly, and powerful Backup & Recovery solution for RHV. It does not require any big Mediaservers or clients running on the VMs that are getting protected.
TrilioVault architecture reflects these principles.
The TrilioVault Appliance is the controller of TrilioVault, called TVM.
The TVM is running and managing all Backup and Recovery Jobs.
During a Backup Job is the TVM:
gathering the Metadata information generated of the VMs that are getting protected
Writing the Metadata information onto the Backup Target
Generating the RHV Snapshot
Sending the data copy commands to the ovirt-imageio services
The TVM is available as qcow2 image and runs as VM on top of a KVM Hypervisor.
It is supported and recommended to run the TVM in the same RHV environment, that the TVM protects.
TrilioVault is natively integrating into the available RHV-M Web Gui, providing a new tab "Backup".
All functionalities of TrilioVault are accessible through the Web Gui.
The RHV-Manager GUI integration is getting installed using Ansible-playbooks together with the ovirt-imageio-proxy extension.
Ovirt-imageio is an RHV internal python service that allows the upload and download of disks into and out of RHV.
The default ovirt-imageio services only allow to move the disks through the RHV-M via https.
TrilioVault extends the ovirt-imageio functionality to provide movement of the disk data through NFS over the RHV Hosts themselves.
The ovirt-imageio extensions are getting installed using Ansible-playbooks.
TrilioVault is writing all Backups over the network using the NFS protocol to a provided Backup Target.
Any system utilizing the NFSv3 protocol is usable.
