starlingx/docs
Code Issues Proposed changes
docs/doc/source/backup/openstack/back-up-openstack.rst
Rafael Jardim d6fb867888 Upstreaming WRO 
Removed duplicate abbrev definitions

Signed-off-by: Rafael Jardim <rafaeljordao.jardim@windriver.com>
Change-Id: I7910d9f54e158250004abd7e17a4e119f8064252
Signed-off-by: Ron Stone <ronald.stone@windriver.com>
2021-03-31 08:57:23 -04:00

1.5 KiB
Raw Blame History

Back up OpenStack

is backed up using the back-up facilities.

The backup playbook will produce a OpenStack backup tarball in addition to the platform tarball. This can be used to perform restores independently of restoring the underlying platform.

Note

Data stored in Ceph such as Glance images, Cinder volumes or volume backups or Rados objects (images stored in ceph) are not backed up automatically.

  • To backup glance images use the image_backup.sh script. For example:

    ~(keystone_admin)$ image-backup export <uuid>

  • To back-up other Ceph data such as cinder volumes, backups in ceph or rados objects use the rbd export command for the data in OpenStack pools cinder-volumes, cinder-backup and rados.

    For example if you want to export a Cinder volume with the ID of: 611157b9-78a4-4a26-af16-f9ff75a85e1b you can use the following command:

    ~(keystone_admin)$ rbd export -p cinder-volumes
611157b9-78a4-4a26-af16-f9ff75a85e1b
/tmp/611157b9-78a4-4a26-af16-f9ff75a85e1b

    To see the the Cinder volumes, use the openstack volume-list command.

    After export, copy the data off-box for safekeeping.

For details on performing a back-up, see System Backup and Restore <backing-up-starlingx-system-data>.