TVO-4.1
Deployment Guide
TrilioVault Appliance Administration Guide
Admin Guide
Troubleshooting
TrilioVault for OpenStack Architecture
Backup-as-a-Service
Trilio is like a Data Protection project providing Backup-as-a-Service
TrilioVault is an add on service to OpenStack cloud infrastructure and provides backup and disaster recovery functions for tenant workloads. TrilioVault is very similar to other OpenStack services including nova, cinder, glance, etc and adheres to all tenets of OpenStack. It is a stateless service that scales with your cloud.
Main Components
TrilioVault architecture overview
TrilioVault has four main software components:
- 1.TrilioVault ships as a QCOW2 image. User can instantiate one or more VMs from the QCOW2 image on a standalone KVM boxes.
- 2.TrilioVault API is a python module that is installed on all OpenStack controller nodes where the nova-api service is running.
- 3.TrilioVault Datamover is a python module that is installed on every OpenStack compute nodes
- 4.TrilioVault horizon plugin is installed as an add on to horizon servers. This module is installed on every server that runs horizon service.
Service Endpoints
Service endpoints overview
TrilioVault is both a provider and consumer into OpenStack ecosystem. It uses other OpenStack services such as nova, cinder, glance, neutron, and keystone and provides its own service to OpenStack tenants. To accomodate all possible OpenStack deployments, TrilioVault can be configured to use either public or internal URLs of services. Likewise TrilioVault provides its own public, internal and admin URLs.
Network Topology
Example network topology
This figure represents a typical network topology. TrilioVault exposes its public URL endpoint on public network and TrilioVault virtual appliances and data movers typically use either internal network or dedicated backup network for storing and retrieving backup images from backup store.
Last modified 11mo ago
Export as PDF
Copy link