Skip to content

updated backup command #1373

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
openshift-merge-bot merged 4 commits into from
May 6, 2026
Merged

updated backup command #1373

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
9463fa7
fixed linting error
klgill May 1, 2026
f5bbdbc
Update docs_user/modules/proc_adopting-the-block-storage-service.adoc
klgill May 4, 2026
513efd6
Update docs_user/modules/proc_adopting-the-block-storage-service.adoc
klgill May 4, 2026
01972de
Apply suggestion from @klgill
klgill May 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions docs_user/modules/proc_adopting-the-block-storage-service.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -349,13 +349,18 @@ $ openstack volume backup list
$ openstack volume create --image cirros --bootable --size 1 disk_new
----

.. Back up the previous attached volume:
.. If you deployed and adopted the `cinder-backup` service, back up the previously attached volume:
+
----
$ openstack --os-volume-api-version 3.47 volume create --backup <backup_name>
$ openstack volume backup create <volume_name> --name <backup_name>
----
+
* Replace `<backup_name>` with the name of your new backup location.
where:

`<volume_name>`:: Specifies the volume that you want to back up.
Replace `<volume_name>` with the volume you want to back up.
`<backup_name>`:: Specifies the name of your new backup.
Replace `<backup_name>` with the name of your new backup.
+
[NOTE]
You do not boot a {compute_service_first_ref} instance by using the new `volume from` image or try to detach the previous volume because the {compute_service} and the {block_storage} are still not connected.
Expand Down
Loading