The TrilioVault Appliance requires configuration to work with the chosen RHV environment. A Web-UI provides access to the TrilioVault Appliance dashboard and configurator.
Enter the TrilioVault IP or FQDN into the browser to reach the TrilioVault Appliance landing page.
User: admin Password: password
Upon login into the TrilioVault Appliance, the shown page is the configurator. The configurator requires some information about the TrilioVault Appliance, RHV and Backup Storage.
The TrilioVault Appliance needs to be integrated into an existing environment to be able to operate correctly. This block asks for information about the TrilioVault Appliance operating details.
Virtual IP Address
The TrilioVault Appliance uses this IP address for all communication with RHV.
TVM Appliance IP
The first interface in the interface list of the TrilioVault Appliance will get this IP address assigned. Further is the TrilioVault Appliance hostname set.
The DNS server the TrilioVault appliance will use.
Format: Comma separated list of IPs
Domain Search Order
The domain the TrilioVault Appliance will use.
Format: Comma separated list of domain names
NTP Servers the TrilioVault Appliance will use.
Format: Comma separated list of NTP Servers (FQDN and IP supported)
Timezone the TrilioVault will use.
Format: predefined list
The TrilioVault appliance integrates with one RHV environment. This block asks for the information required to access and connect with the RHV Cluster.
RHV Engine URL
URL of the RHV-Manager used to authenticate
Format: URL (FQDN and IP supported)
The password to validate the RHV Username against the RHV-Manager
This block asks for the necessary details to configure the Backup Storage.
NFS or S3
Full path to the NFS Volume used as Backup Storage
Format: Comma separated list of NFS paths
Options used by the TrilioVault NFS client to connect to the NFS Volume
Format: NFS Options
Note:- Make sure the NFS server supports the NFSv3 as Trilio Mounts the NFS share explicitly with NFSv3
Amazon or Ceph or Local Ceph
Amazon expects to connect to AWS services
Ceph allows connecting to any S3 bucket that is either not using SSL or a trusted SSL certificate
Local Ceph allows connecting to any S3 that is either not using SSL or a self-signed certificate
[Ceph and Local Ceph only] Use SSL
Activate when the S3 endpoint is secured
Access Key necessary to login into the S3 storage
format: access key
Secret Key necessary to login into the S3 storage
format: secret key
Configured Region for the S3 Bucket
use us-east-1 for Ceph and Local Ceph
[Ceph and Local Ceph only] Endpoint URL
URL to be used to reach and access the provided S3 compatible storage
Name of the bucket to be used as Backup target
[Local Ceph with active SSL only] Cert
Upload area for the certificate to be used when connecting with the S3 storage
TrilioVault is integrating into the RHV Cluster as an additional service, following the RHV communication paradigms. These require that the TrilioVault Appliance is using SSL and that the RHV-Manager does trust the TrilioVault Appliance.
TrilioVault offers to possibilities how these required certificates can be provided. Either TrilioVault generates a complete fresh self-signed certificate or a certificate is provided.
In both cases is the FQDN required, to which the certificate is pointing to.
Please see below example in case of a provided certificate.
FQDN to reach the TrilioVault Appliance
Certificate provided by the TrilioVault appliance upon request
Format: Certificate file
Private Key used to verify the provided certificate
Format: private key file
It is possible to directly provide the TrilioVault Appliance with the license file that is going to be used by it.
It is not necessary to provide the License file directly through the configurator. It is also possible to provide the license afterwards through the TrilioVault License tab in the TrilioVault dashboard.
The TrilioVault License tab can also be used to verify and update the currently installed license.
After filling out every block of the configurator, hit the submit button to start the configuration.
The configurator asks one more time for confirmation before starting.
While the configurator is running the live output from the ansible playbooks is shown. Some of the tasks can take multiple minutes until they are finished without an update to the output.
Wait until the configurator has either finished or failed.