Switch NFS Backing file
TrilioVault is using a base64 hash for the mount point of NFS Backup targets. This hash makes sure, that multiple NFS Shares can be used with the same TrilioVault installation.
This base64 hash is part of the TrilioVault incremental backups as an absolute path of the backing files. This requires the usage of mount bind during a DR scenario or quick migration scenario.
In the case that there is time for a thorough migration there is another option to change the backing file and make the TrilioVault backups available on a different NFS Share. This option is updating the backing file to the new NFS Share mount point.
TrilioVault is providing a shell script for the purpose of changing the backing file. This script is used after the TrilioVault appliance has been reconfigured to use the new NFS share.
The Shell script is publicly available at:
Please ask your Trilio Customer Success Manager or Engineer.This page will be updated once the script is publicly available.
The following requirements need to be met before the change of the backing file can be attempted.
The TrilioVault Appliance has been reconfigured with the new NFS Share
Please check here for reconfiguring the TrilioVault Appliance
The workloads are available on the new NFS Share
The workloads are owned by nova:nova user
The shell script is changing one workload at a time.
The shell script has to run as nova user, otherwise the owner will get changed and the backup can not be used by TrilioVault.
Run the following command:
./backing_file_update.sh /var/triliovault-mounts/<base64>/workload_<workload_id>
with
/var/triliovault-mounts/<base64>/being the new NFS mount pathworkload_<workload_id>being the workload to rebase
The shell script is generating the following log file at the following location:
/tmp/backing_file_update.log
The log file will not get overwritten when the script is run multiple times. Each run of the script will append the available log file.