This procedure is designed to be applicable to all Openstack installations using TrilioVault. 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.
TrilioVault incremental Snapshots involve a backing file to the prior backup taken, which makes every TrilioVault incremental backup a synthetic full backup.
TrilioVault is using qcow2 backing files for this feature:
qemu-img info 85b645c5-c1ea-4628-b5d8-1faea0e9d549
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.
TrilioVault 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
When the path of the backing file is not available on the TrilioVault 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.