Chapter 7. Backing up important files
Backing up important configuration files, inventory files, and modified playbooks makes it easy to restore or redeploy your cluster.
Red Hat recommends backing up your configuration after initial deployment, and after confirming the success of any major changes in your cluster. You can also take backups after a node has failed if necessary.
Example playbooks and inventory files are stored in the
/etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deploymentdirectory. If you have manually created or modified inventory and playbook files and you are not storing them in this directory, ensure that you know the path to their location.
- Log in to a hyperconverged host as the root user.
Change into the
hc-ansible-deploymentdirectory and back up the default
# cd /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment # cp archive_config_inventory.yml archive_config_inventory.yml.bk
archive_config_inventory.ymlfile with details of the cluster you want to back up.
- The backend FQDN of each host in the cluster that you want to back up.
- The directory in which to store backup files.
If you use Network-Bound Disk Encryption, set this to
true. Otherwise, set to
all: hosts: host1-backend.example.com: host2-backend.example.com: host3-backend.example.com: vars: backup_dir: /rhhi-backup nbde_setup: true upgrade: false
archive_config.ymlplaybook using your updated inventory file with the
# ansible-playbook -i archive_config_inventory.yml archive_config.yml --tags=backupfiles
This creates an archive in the
/rootdirectory specific to each host FQDN in the
hostssection of the inventory, for example,
Transfer the backup archives to a different machine.
# scp /root/rhvh-node-host1-backend.example.com-backup.tar.gz backup-host.example.com:/backups/