Switch Backup Target on Kolla-ansible
The first step is to remove the datamover container and to unmount the old mounts. This is necessary to make sure, that the new datamover container with the new backend target is not getting any interference from the old backup target.
#check current mount point[[email protected] ~]# df -hFilesystem Size Used Avail Use% Mounted ondevtmpfs 7.8G 0 7.8G 0% /devtmpfs 7.8G 0 7.8G 0% /dev/shmtmpfs 7.8G 26M 7.8G 1% /runtmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup/dev/mapper/cl-root 280G 12G 269G 5% //dev/sda1 976M 197M 713M 22% /boot192.168.1.34:/mnt/tvault/42436 2.5T 1005G 1.5T 41% /var/trilio/triliovault-mounts/MTkyLjE2OC4xLjM0Oi9tbnQvdHZhdWx0LzQyNDM2#Stop triliovault_datamover[[email protected] ~]# docker stop triliovault_datamovertriliovault_datamover[[email protected] ~]##Delete triliovault_datamover[[email protected] ~]# docker rm triliovault_datamovertriliovault_datamover[[email protected] ~]##unmount mount point[[email protected] ~]# umount /var/trilio/triliovault-mounts/MTkyLjE2OC4xLjM0Oi9tbnQvdHZhdWx0LzQyNDM2#check mount point is unmounted successfully[[email protected] ~]# df -hFilesystem Size Used Avail Use% Mounted ondevtmpfs 7.8G 0 7.8G 0% /devtmpfs 7.8G 0 7.8G 0% /dev/shmtmpfs 7.8G 26M 7.8G 1% /runtmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup/dev/mapper/cl-root 280G 12G 269G 5% //dev/sda1 976M 197M 713M 22% /boot[[email protected] ~]##Delete mounted dir from compute node[[email protected] trilio]# rm -rf /var/trilio/triliovault-mounts/MTkyLjE2OC4xLjM0Oi9tbnQvdHZhdWx0LzQyNDM2
Edit the globals.yml file to contain the new backup target.
Follow the installation documentation to learn about the globals.yml TrilioVault variables.
[email protected]:~# kolla-ansible -i multinode deploy
##Check that all Containers are up and running#Controller node[email protected]:~# docker ps -a | grep trilio583b8d42ab42 trilio/ubuntu-binary-trilio-datamover-api:4.1.36-ussuri "dumb-init --single-…" 3 days ago Up 3 days openstack-nova-api-triliodata-plugin3be25d3819ac trilio/ubuntu-binary-trilio-horizon-plugin:4.1.36-ussuri "dumb-init --single-…" 4 days ago Up 4 days horizon#Compute node[email protected]:~# docker ps -a | grep triliobf52face23fb trilio/ubuntu-binary-trilio-datamover:4.1.36-ussuri "dumb-init --single-…" 3 days ago Up 3 days trilio-datamover## Verify the backup target has been changed successfully# In case of switch to NFS[[email protected] ~]# df -hFilesystem Size Used Avail Use% Mounted ondevtmpfs 7.8G 0 7.8G 0% /devtmpfs 7.8G 0 7.8G 0% /dev/shmtmpfs 7.8G 26M 7.8G 1% /runtmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup/dev/mapper/cl-root 280G 12G 269G 5% //dev/sda1 976M 197M 713M 22% /boot192.168.1.34:/mnt/tvault/42436 2.5T 1005G 1.5T 41% /var/trilio/triliovault-mounts/MTkyLjE2OC4xLjM0Oi9tbnQvdHZhdWx0LzQyNDM2#In case of switch to S3[[email protected] ~]# df -hFilesystem Size Used Avail Use% Mounted ondevtmpfs 7.8G 0 7.8G 0% /devtmpfs 7.8G 0 7.8G 0% /dev/shmtmpfs 7.8G 34M 7.8G 1% /runtmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup/dev/mapper/cl-root 280G 12G 269G 5% //dev/sda1 976M 197M 713M 22% /bootTrilioVault - - 0.0K - /var/trilio/triliovault-mounts##Reverify in the triliovault_datamover containers[[email protected] ~]# docker exec -it triliovault_datamover bash(triliovault-datamover)[[email protected] /]$ df -hFilesystem Size Used Avail Use% Mounted onoverlay 280G 12G 269G 5% /tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroupdevtmpfs 7.8G 0 7.8G 0% /devtmpfs 7.8G 0 7.8G 0% /dev/shm/dev/mapper/cl-root 280G 12G 269G 5% /etc/iscsitmpfs 6.3G 0 6.3G 0% /var/triliovault/tmpfsTrilioVault - - 0.0K - /var/trilio/triliovault-mounts
Follow the documentation to reconfigure the TrilioVault appliance with the new backup target.