starlingx/docs
Code Issues Proposed changes
Files
bb66b3373c62c36e4eb0e955bb0e95ef72d39a9c
docs/doc/source/backup/openstack/restore-openstack-from-a-backup.rst
Ron Stone 802aa99c1b Openstack .. include changes 
Made paths to include files relative to doc source. This is needed for downstream builds
and is good practice for reusability.
Fixed some include statements with broken syntax.
Added missing section labels to include file.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: I0423c2008445b49e0bb60b9690925041d7acd6f6
Signed-off-by: Ron Stone <ronald.stone@windriver.com>
2021-06-22 08:36:11 -04:00

27 KiB
Raw Blame History

Restore OpenStack from a Backup

You can restore from a backup with or without Ceph.

  • You must have a backup of your installation as described in Back up OpenStack <back-up-openstack>.
  • You must have an operational deployment.

  1. Delete the old OpenStack application and upload it again.

    Note

    Images and volumes will remain in Ceph.

    ~(keystone_admin)$ system application-remove wr-openstack
~(keystone_admin)$ system application-delete wr-openstack
~(keystone_admin)$ system application-upload wr-openstack.tgz

  2. Restore .

    You can choose either of the following options:

    • Restore only system. This option will not restore the Ceph data (that is, it will not run comands like rbd import). This procedure will preserve any existing Ceph data at restore-time.
    • Restore system data, Cinder volumes and Glance images. You'll want to run this step if your Ceph data will be wiped after the backup.
    Restore only OpenStack application system data:

    1. Run the following command:

      ~(keystone_admin)$ ansible-playbook /usr/share/ansible/stx-ansible/playbooks/ \
restore_openstack.yml \
-e 'initial_backup_dir=<location_of_backup_filename> \
ansible_become_pass=<admin_password> \
admin_password=<admin_password> \
backup_filename=wr-openstack_backup.tgz'
    Restore OpenStack application system data, cinder volumes and glance images:

    1. Run the following command:

      ~(keystone_admin)$ ansible-playbook /usr/share/ansible/stx-ansible/playbooks/ \
restore_openstack.yml \
-e 'restore_cinder_glance_data=true \
initial_backup_dir=<location_of_backup_filename> \
ansible_become_pass=<admin_password> \
admin_password=<admin_password> \
backup_filename=wr-openstack_backup.tgz'

    When this step has completed, the Cinder, Glance and MariaDB services will be up, and Mariadb data restored.

    1. Restore Ceph data.
      1. Restore Cinder volumes using rbd import command.

    For example:

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

    Where tmp/611157b9-78a4-4a26-af16-f9ff75a85e1b is a file saved earlier at the backup procedure as described in .

    1. Restore Glance images using the image-backup script.

    For example if we have an archive named image_3f30adc2-3e7c-45bf-9d4b-a4c1e191d879.tgz in the/opt/backups directory we can use restore it using the following command:

    ~(keystone_admin)$ sudo image-backup.sh import image_3f30adc2-3e7c-45bf-9d4b-a4c1e191d879.tgz

    1. Use the tidy\_storage\_post\_restore utilitary to detect any discrepancy between Cinder/Glance DB and rbd pools:

      ~(keystone_admin)$ tidy_storage_post_restore <log_file>

    After the script finishes, some command output will be written to the log file. They will help reconcile discrepancies between the database and CEPH data.

    1. Run the playbook again with the restore_openstack_continue flag set to true to bring up the remaining Openstack services.

      ~(keystone_admin)$ ansible-playbook /usr/share/ansible/stx-ansible/playbooks/ \
restore_openstack.yml \
-e 'restore_openstack_continue=true \
initial_backup_dir=<location_of_backup_filename>
ansible_become_pass=<admin_password> \
admin_password=<admin_password> \
backup_filename=wr-openstack_backup.tgz'