openstack/openstack-ansible
Code Issues Proposed changes

[docs] Add backup information to the OSA Ops Guide

Browse Source 
Corrected capital S in OpenStack-Ansible

Change-Id: Id15335234bdaf612f6d56166d2086c2ab02c7508
Implements: blueprint create-ops-guide
This commit is contained in:
daz 2017-04-06 15:45:56 +10:00 committed by Alexandra Settle
parent 337fb6b004
commit 936610a6be
1 changed files with 21 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

40
doc/source/draft-operations-guide/maintenance-tasks/backups.rst
View File

@ -1,26 +1,28 @@
=======
Backups
=======
========
Back ups
========
Creating backups of database
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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.
Content to be written. Patches welcome!
Back up and restore the ``/etc/openstack_deploy/`` directory
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Restoring the database
~~~~~~~~~~~~~~~~~~~~~~
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.
Content to be written. Patches welcome!
To restore the ``/etc/openstack_deploy/`` directory, copy the backup of the
directory to your cloud environment.
`Backup Recovery <https://docs.openstack.org/ops-guide/ops-backup-recovery.html>`_
Backup of /etc/openstack_deploy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Save the files into a remote location. They hold live inventory, host
structure, network information, passwords and many other variables.
Restore /etc/openstack_deploy
Database backups and recovery
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Copy the files back. Simple as that.
MySQL data is automatically backed up. To recover the database, use the
database backups and rebuild the Galera cluster. For more information, see
:ref:`galera-cluster-maintenance`.