From 5ce60bd91101dba94dd7ecb683fc4e3e0eee2d39 Mon Sep 17 00:00:00 2001 From: Joseph Robinson Date: Fri, 11 Sep 2015 16:01:11 +1000 Subject: [PATCH] Additional options for cinder backup-list Adding information on the new optional arguments for the cinder backup-list command to the cloud admin guide. Change-Id: I5fb0b4c0e49edc88d772a47f444f50b4f5f0354f Closes-Bug: #1486677 --- .../source/blockstorage_volume_backups.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/doc/admin-guide-cloud/source/blockstorage_volume_backups.rst b/doc/admin-guide-cloud/source/blockstorage_volume_backups.rst index 815c6de768..c614a29bec 100644 --- a/doc/admin-guide-cloud/source/blockstorage_volume_backups.rst +++ b/doc/admin-guide-cloud/source/blockstorage_volume_backups.rst @@ -58,6 +58,13 @@ on the IDs of the parent backups. A full restore is performed based on the full backup first, then restore is done based on the incremental backup, laying on top of it in order. +You can view a backup list with the :command:`cinder backup-list` +command. Optional arguments to clarify the status of your backups +include: running ``--name``, ``--status``, and ``--volume-id`` to filter +through backups by the specified name, status, or volume-id. Search +with ``--all-tenants`` for details of the tenants associated +with the listed backups. + Because volume backups are dependent on the Block Storage database, you must also back up your Block Storage database regularly to ensure data recovery.