TrilioVault 3.7 Release Notes
TrilioVault 3.7 is the third release of TrilioVault for Red Hat Virtualization.
It is aimed to provide Backup and Recovery for Red Hat Virtualization 4.2.8 & 4.3.x. The full requirements can be found here.
TrilioVault 3.7 Features on a Glance
New Feature: File Recovery
TrilioVault 3.7 introduces the File Recovery to TrilioVault for RHV.
It is now possible to recover single files from any backups by downloading the files through the RHV-M
This feature is provided in two ways:
For files smaller than 2GB it is possible to download the file directly through the file search
It is possible to mount and browse a Snapshot to go to a file location and download it directly without any size limits.
New Feature: RestFul API
TrilioVault 3.7 makes the RestFul API of the TrilioVault Appliance available to use.
This feature allows to integrate TrilioVault 3.7 into any orchestration tool capable of using a RestFul API.
Known limitations
Large Size backups failing with error - "Could not initialize session: Unable to verify proxy ticket"
RHV has a limitation of 10hours for a disk's transfer session, which cannot be altered. RHV setups on slower networks will face this issue.
Ansible imageio daemon/proxy script execution interruption can leave imageio unstable
In the case of the Ansible playbooks installing the ovirt-imageio extensions being interrupted is it possible that the ovirt-image io version are getting unstable and no longer usable.
Workaround: Uninstall the ovirt-imageio extension and install them again.
RHV Snapshot changing preallocated disktypes to thinprovisioned
RHV Snapshots are always thin-provisioned qcow2 images. These qcow2 images are the active images for the VM running and they are the qcow2 backing file capability to point to the original image. That's why the disktype is changing from preallocated to thinprovisioned upon snapshotting.
Manual deletion or cancelling of any Snapshot from TVM promotes next snapshot to be Full
Manual deletion of Snapshots is only expected to happen, when an error occurred that got not identified by TrilioVault during the backup process. To prevent possible data loss is the next Snapshot upgraded to a Full Snapshot.
Workloads are getting created for unprotected hosts
The list of available VMs is taken from the RHV-Manager and every VM not part of a Snapshot can be included in a workload. It is not checked if the Virtual Machines are running on RHV-Hosts that do not have the ovirt-imageio-daemon extension installed.
TrilioVault requires all RHV-Hosts to have the ovirt-imageio-daemon extension to be installed.
File search is case sensitive
TrilioVault is providing filesearch through libguestfs and therefor bound by any libguestfs limitations.
Known issues
VMs being retsored from RHV 4.2 to 4.3 might need changing the custom compatibility version
TrilioVault is storing and restoring the VM with all its configurations, including the compatibility version tied to a RHV release. Upon a restore might the VM fail to power up after the restore. The restore itself succeeds.
Workaround: Edit the VM configuration and update the compatibility version.
Import Workloads gives Gateway Timeout error on UI
Importing a bigger amount of Workloads with many Snapshots leads to the TrilioVault Dashboard refresh timing out before the import has finished. The import is continuing in the background as desired.
Recommendation: Verify from the RHV-M or via TrilioVault API the amount of available workloads.
Create Workload window does not disappear while creating large (>150 VMs) workloads
While the workload is being created on the TrilioVault Appliance is the RHV-M integration waiting for the workload creation successful signal to close the create workload window. The workload creation is continuing as desired.
TVM Reconfiguration requires manual restart of services
During reconfiguration it is possible that the configurator fails during nginx service restart or wlm-api restart.
Workaround: Restart nginx and wlm-api services manually before retrying the configuration.
Snapshots fail with 500 error "Server failed to performed the request" after server restart
After restarting the RHV-Hosts it is possible that the communication between Redis and ovirt_celery is broken.
Rerunning the Ansible-Playbooks for all RHV-Hosts fixes this issue.
Restarting the TrilioVault during a running Snapshot leads to Snapshot getting stuck in execution state
Restarting the TrilioVaut VM will stop any ongoing backup or restore processes on the TrilioVault Appliance. This can lead to the Snapshot status not being updated in the TrilioVault database, leaving them stuck in execution state without any task connected to them.
Further Snapshots are not getting affected. Please contact Customer Success for help in moving stuck Snapshots into the error state.
Last updated