Files
openstack-ansible/doc/source/admin/maintenance-tasks/backups.rst
Jesse Pretorius 315780f350 March to the beat of the new docs drum
Boss drum, motivating rhythm of life with the
healing, rhythmic synergy.

More seriously, this patch re-arranges the
documentation structure to conform to the
structure outlined in [1].

With it, some changes are made to effectively
transition the links and simplify the sphinx
configuration.

The Mitaka/Liberty documentation links are
removed as they are no longer available.

[1] http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html
Change-Id: Icc985de3af4de5ea7a5aa01b6e6f6e524c67f11b
2017-07-05 09:13:13 +00:00

1.1 KiB

Back ups

For disaster recovery purposes, it is a good practice to perform regular backups of the database, configuration files, network information, and OpenStack service details in your environment. For an OpenStack cloud deployed using OpenStack-Ansible, back up the /etc/openstack_deploy/ directory.

Back up and restore the /etc/openstack_deploy/ directory

The /etc/openstack_deploy/ directory contains a live inventory, host structure, network information, passwords, and options that are applied to the configuration files for each service in your OpenStack deployment. Back up the /etc/openstack_deploy/ directory to a remote location.

To restore the /etc/openstack_deploy/ directory, copy the backup of the directory to your cloud environment.

Database backups and recovery

MySQL data is automatically backed up. To recover the database, use the database backups and rebuild the Galera cluster. For more information, see galera-cluster-maintenance.