Comment on page

General requirements

TrilioVault is a pure software solution and is composed of 3 elements:
  1. 1.
    TrilioVault Controller Cluster
  2. 2.
    TrilioVault RHV-M Web-GUI extension
  3. 3.
    TrilioVault Datamover

System requirements TrilioVault Controller Cluster

The TrilioVault Controller Cluster consists of multiple containers:
  • rhv-configurator - this container contains all configuration UI used to configure the Triliovault solution after deployment
  • config-api - this container is responsible to deploy and configure the actual TrilioVault solution after all values are provided through the configuration UI
  • wlm-api - this container provides the api used by the RHV-M integration to work with workloads, backups and restores
  • wlm-scheduler - this container takes jobs from the wlm-api and schedules them on a wlm-workloads container. It hereby chooses the wwlm-workloads container with the lowest load
  • MariaDB - this container provides the TrilioVault database
  • RabbitMQ - this container provides the RabbitMQ service used internally by the TrilioVault solution
The TrilioVault Controller Cluster consists of 3 VMs fulfilling the following base requirements
Ressource
Value
vCPU
6
RAM
16 GB
Disk
100 GB
Operating System
RHEL 8

System requirements TrilioVault datamover

TrilioVault is installing the TrilioVault datamover service next to the ovirt-imageio-proxy service running on the RHV-Manager and ovirt-imageio-daemon running on the RHV-Hosts.
The TrilioVault datamover doesn't have any hardware-related requirements, but they require specific versions of the ovirt-imageio services.
Please check the Support Matrix for further information.
The installed versions of the ovirt-imageio-proxy and the ovirt-imageio-daemon need to be the same.