Block storage how-to guides
Overview
Block storage how-to guides
Procedural guides for block storage volumes: creating, resizing, cloning, snapshotting, and transferring volumes between projects. For background on volume lifecycle and how snapshots and clones differ, see Volumes.
- How to Clone a Block Storage Volume: Create an independent copy of an existing volume. The clone is a new, fully writable volume. Changes to the clone do not affect the source, and vice versa. You can clone a source volume whether it is...
- How to Create a Block Storage Volume: Create a persistent block storage volume that you can attach to virtual machine instances. Volumes persist independently of instances; you can detach, reattach, and snapshot them at any time.
- How to Create a Volume Snapshot: Create a point-in-time snapshot of a block storage volume. Snapshots are space-efficient: they store only the difference from the volume's base state, and you can use them to create new volumes or...
- How to Extend a Block Storage Volume: Increase the capacity of an existing block storage volume. Volume extensions are irreversible: capacity can only grow. Quake AI's Cinder supports online extend on an attached, in-use volume when you...
- How to Schedule Volume Snapshots and Restore Data: Schedule recurring Cinder volume snapshots with cron on a control instance or a CI workflow. Set a retention period, remove expired snapshots, and test restores on a recovery volume.
- How to Transfer Volume Ownership Between Projects: Move a block storage volume from one Quake AI project to another. The source project creates a transfer record. The target project accepts the record with the transfer ID and authorization key.
Quick answers
Common Block Storage tasks
See Also
Was this page helpful?