LogoLogo
T4O-4.0
T4O-4.0
  • About Trilio for Openstack
  • Trilio for Openstack Architecture
  • Trilio 4.0 Release Notes
  • Deployment Guide
    • Support Matrix
    • Requirements
    • Trilio network considerations
    • Preparing the installation
    • Spinning up the Trilio VM
    • Installing Trilio Components
      • Installing on RHOSP13
      • Installing on RHOSP16.0
      • Installing on RHOSP16.1
      • Installing on Canonical Openstack Queens and Train
      • Installing on Kolla Train
      • Installing on Ansible Openstack Train
    • Configuring Trilio
    • Apply the Trilio license
    • Additions for multiple CEPH configurations
    • Post Installation Health-Check
    • Uninstall Trilio
    • Upgrade Trilio
      • Ubuntu/Debian based Openstack enviroments
      • CentOS/RHEL based Openstack environments
      • RHOSP Upgrade
      • Upgrade Trilio Appliance
    • Uploading the File Recovery Manager
    • Install workloadmgr CLI client
  • Trilio Appliance Administration Guide
    • Trilio Appliance Dashboard
    • Reconfigure the Trilio Cluster
    • Change the Trilio GUI password
    • Reset the Trilio GUI password
    • Reinitialize Trilio
    • Set the Trilio Openstack service password
    • Available downloads from the Trilio Cluster
  • User Guide
    • Workloads
    • Snapshots
    • Restores
    • File Search
    • Snapshot Mount
    • Schedulers
    • E-Mail Notifications
  • Admin Guide
    • Backups-Admin Area
    • Workload Policies
    • Workload Quotas
    • Managing Trusts
    • Workload Import & Migration
    • Disaster Recovery
      • Example runbook for Disaster Recovery using NFS
  • Troubleshooting
    • General Troubleshooting Tips
    • Example RC file for workloadmgr CLI
    • Using the workloadmgr CLI tool on the Trilio Appliance
    • Healthcheck of Trilio
    • Important log files
  • API GUIDE
    • Workloads
    • Snapshots
    • Restores
    • File Search
    • Snapshot Mount
    • Schedulers
    • E-Mail Notifications Settings
    • Workload Policies
    • Workload Quotas
    • Managing Trusts
    • Workload Import and Migration
Powered by GitBook
On this page
  • Disaster Recovery Process
  • Mount-paths

Was this helpful?

Export as PDF
  1. Admin Guide

Disaster Recovery

PreviousWorkload Import & MigrationNextExample runbook for Disaster Recovery using NFS

Last updated 1 year ago

Was this helpful?

Trilio Workloads are designed to allow a Desaster Recovery without the need to backup the Trilio database.

As long as the Trilio Workloads are existing on the Backup Target Storage and a Trilio installation has access to them, it is possible to restore the Workloads.

Disaster Recovery Process

  1. and Trilio for the target cloud

  2. Notify users to of Workloads being available

This procedure is designed to be applicable to all Openstack installations using Trilio. It is to be used as a starting point to develop the exact Desaster Recovery process of a specific environment.

In case that instead of noticing the users, the workloads shall be restored is it necessary to have an User in each Project, that has the necessary privileges to restore.

Mount-paths

Trilio incremental Snapshots involve a backing file to the prior backup taken, which makes every Trilio incremental backup a synthetic full backup.

Trilio is using qcow2 backing files for this feature:

qemu-img info 85b645c5-c1ea-4628-b5d8-1faea0e9d549
image: 85b645c5-c1ea-4628-b5d8-1faea0e9d549
file format: qcow2
virtual size: 1.0G (1073741824 bytes)
disk size: 21M
cluster_size: 65536
backing file: /var/triliovault-mounts/MTAuMTAuMi4yMDovdXBzdHJlYW0=/workload_3c2fbee5-ad90-4448-b009-5047bcffc2ea/snapshot_f4874ed7-fe85-4d7d-b22b-082a2e068010/vm_id_9894f013-77dd-4514-8e65-818f4ae91d1f/vm_res_id_9ae3a6e7-dffe-4424-badc-bc4de1a18b40_vda/a6289269-3e72-4085-adca-e228ba656984
Format specific information:
    compat: 1.1
    lazy refcounts: false
    refcount bits: 16
    corrupt: false

As can be seen in the example is the backing file an absolute path, which makes it necessary, that this path exists so the backing files can be accessed.

Trilio is using the base64 hashing algorithm for the NFS mount-paths, to allow the configuration of multiple NFS Volumes at the same time. The hash value is calculated using the provided NFS path.

# echo -n 10.10.2.20:/upstream | base64
MTAuMTAuMi4yMDovdXBzdHJlYW0=

When the path of the backing file is not available on the Trilio appliance and Compute nodes, will the restores of incremental backups fail.

The tested and recommended method to make the backing files available is creating the required directory path and using mount --bind to make the path available for the backups.

#mount --bind <mount-path1> <mount-path2>

Running the mount --bind command will make the necessary path available until the next reboot. If it is required to have access to the path beyond a reboot is it necessary to edit the fstab.

#vi /etc/fstab
<mount-path1> <mount-path2>	none bind	0 0
Install
Configure
Verify required mount-paths and create if necessary
Reassign Workloads