Ce contenu n'est pas disponible dans la langue sélectionnée.

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.

Prerequisites

  • Example playbooks and inventory files are stored in the /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment directory. 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.

Procedure

  1. Log in to a hyperconverged host as the root user.
  2. Change into the hc-ansible-deployment directory and back up the default archive_config_inventory.yml file.

    # cd /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment
    # cp archive_config_inventory.yml archive_config_inventory.yml.bk
    Copy to Clipboard Toggle word wrap
  3. Edit the archive_config_inventory.yml file with details of the cluster you want to back up.

    hosts
    The backend FQDN of each host in the cluster that you want to back up.
    backup_dir
    The directory in which to store backup files.
    nbde_setup
    If you use Network-Bound Disk Encryption, set this to true. Otherwise, set to false.
    upgrade
    Set to false.

    For example:

    all:
      hosts:
        host1-backend.example.com:
        host2-backend.example.com:
        host3-backend.example.com:
      vars:
        backup_dir: /rhhi-backup
        nbde_setup: true
        upgrade: false
    Copy to Clipboard Toggle word wrap
  4. Run the archive_config.yml playbook using your updated inventory file with the backupfiles tag.

    # ansible-playbook -i archive_config_inventory.yml archive_config.yml --tags=backupfiles
    Copy to Clipboard Toggle word wrap

    This creates an archive in the /root directory specific to each host FQDN in the hosts section of the inventory, for example, /root/rhvh-node-host1-backend.example.com-backup.tar.gz.

  5. Transfer the backup archives to a different machine.

    # scp /root/rhvh-node-host1-backend.example.com-backup.tar.gz backup-host.example.com:/backups/
    Copy to Clipboard Toggle word wrap
Retour au début
Red Hat logoGithubredditYoutubeTwitter

Apprendre

Essayez, achetez et vendez

Communautés

À propos de la documentation Red Hat

Nous aidons les utilisateurs de Red Hat à innover et à atteindre leurs objectifs grâce à nos produits et services avec un contenu auquel ils peuvent faire confiance. Découvrez nos récentes mises à jour.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Theme

© 2025 Red Hat