TrilioVault 4.1 is the fifth release of TrilioVault for Red Hat Virtualization.
It is aimed to provide Backup and Recovery for Red Hat Virtualization 4.3.x & 4.4.x. The full requirements can be found here.
Image based VMs (iSCSI and NFS)
Template based VMs (iSCSI)
Scheduled based Backup
The usage of Object Storages for Backup purposes is increasing worldwide and TrilioVault for RHV was the last product in the TrilioVault product line, which wasn't supporting the S3 protocol for backup targets.
TVR 4.1 is extending the possible backup targets to all S3 compatible storage solutions.
TrilioVault is integrating native into RHV and has so far required that the user has superuser privileges to be able to work with TrilioVault inside the RHV Manager GUI. This provided Backup administrators with far more permissions than they would require to work with TrilioVault.
TVR 4.1 is introducing role-based access control to TrilioVault features and tasks as follows:
RHV superuser - Can do everything inside RHV including TrilioVault
TrilioBackupAdministrator - Can use TrilioVault completly but can't do anything in RHV except login
TrilioBackup - Can use all backup related features of TrilioVault but can't do anything in RHV except login
TrilioRestore - Can use all restore releated features of TrilioVault but can't do anything in RHV except login
TrilioMonitor - Can generate reports and oversee Workload and Snapshot status but can't do anything in RHV except login
The TriliioVault Appliance GUI has been completly revamped for quicker responses and easier usage.
Accessing the TrilioVault appliance to edit inventory files and run Ansible playbooks was a working solution but didn't have a good usability value.
In TVR 4.1 the installation of the RHV Host and RHV Manager components is done through the TrilioVault Appliance GUI directly.
When running the configurator the user needed to wait until a playbook had fully finished before the output could be reviewed.
In TVR 4.1 the output of the Ansible playbooks are shown live inside the TrilioVault Appliance GUI.
In TVR 4.1 it is possible to set a banner that is shown on the login page of the TrilioVault Appliance.
TVR 4.1 is now logging the following events for the TrilioVault Appliance GUI admin user:
Any login attempts with a different user are also logged with the appropriate error message.
All tasks that needed to be done directly on the TrilioVault appliance during installation, configuration or troubleshooting required the root user, which had far more priviliges than required.
TVR 4.1 is introducing the TVR service user rhv_nw who is capable of doing the following tasks on the TrilioVault Appliance directly:
Change network interface configuration
restart workloadmgr services
TVR 4.1 is not supporting NFSv4. Backups taken using NFSv4 will fail with I/O errors.
Workaround is to enforce the usage of NFSv3 by adding
vers=3 as NFS option.
It is possible to download smaller files directly after a file search. When the user is clicking the download button multiple times without waiting for the download window to appear the wlm-api logs are flooded with error messages.
It is possible to accidently run the installation of the TVR daemon, that is supposed to run on the RHV Hosts only, against the RHV Manager.
The installation will succeed and backups might fail with the following error:
error while converting qcow2: Could not create file: Numerical result out of range\n'
It has been observed that while navigating through mounted Snapshots inside the RHV Manager the UI freezes when directories are accessed, which contain more than 100.000 files.
This might be observed with less files or much more files depending on the transfer speed between TrilioVault appliance and backup target.
In case of Filesearch requiring more than 5 minutes the process fails and a SQL Server gone away error gets logged.
This can happen due to a huge amount of files needed to be searched, which is hitting the limit of the max_allowed_packet handled by MySQL. This value can be increased in
/etc/my.cnf.d/server.conf as shown below.
It has been observed that during the import of many workloads at once that the TrilioVault Appliance GUI returns that the workload import failed, but it is actually ongoing in the background.
The workload import status can be tailed in the wlm-api log.
The wlm-api log is also showing the error message of the NGINX gateway failure (timeout), which is leading to the wrong error message on the GUI.
In case of TrilioVault being uninstalled in a environment are the TrilioVault roles created in RHV left behind and need to be deleted by an administrator manually.