How to create a volume snapshot
Coming from another cloud?
▸AWS·EBS Snapshots
EBS Snapshots
- Per-EBS volume, incremental in S3; not full instance image.
- Via EC2 CreateSnapshot API, not Nova/Cinder.
- Async pending state, volume usable during snapshot.
- Billed per GB-month stored.
▸Azure·Snapshots
Snapshots
- Snapshots of managed disks (Microsoft.Compute/snapshots), billed on used size, separate from volumes unlike Cinder volume snapshots integration.
- Supports incremental snapshots for efficiency, ZRS storage in zones.
- API /providers/Microsoft.Compute/snapshots vs Nova/Cinder volume snapshot APIs.
- Primarily for disks, not full instances; instance snapshots via images instead.
▸DigitalOcean·Volume Snapshots
Volume Snapshots
- Proprietary API /v2/volumes/{volume_id}/snapshots instead of OpenStack /v3/{project_id}/snapshots.
- Explicitly crash-consistent only, no automatic filesystem consistency (requires manual power-off/sync); OpenStack snapshots can use quiescing drivers for apps like databases.
- Snapshots billed separately based on block-level used size (may exceed filesystem due to trim); OpenStack typically similar. See the DigitalOcean pricing page for current rates.
- Can create new volumes only in same region as snapshot; OpenStack snapshots more flexible for cross-region with upload/download.
▸Google Cloud·Standard/Archive Snapshots
Standard/Archive Snapshots
- Crash-consistent point-in-time copies stored incrementally in Cloud Storage (geo-redundant by default), unlike Cinder snapshots which depend on backend (often full copies).
- Two types: Standard (faster recovery) and Archive (cheaper long-term); supports snapshot schedules (standard only).
- Global by default, shareable across projects/regions/zones with network egress costs for cross-region restore; regional scoping (preview) for location control.
- Frequency limit: max 6 snapshots per disk every 60 minutes.
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 restore data.
Prerequisites
- ConsoleLogged in to the Quake AI console
- CLIOpenStack CLI installed and authenticated (
clouds.yamloropenrcsourced) - APIAPI token generated with
$OS_TOKENand service endpoint variables set
Windows: CLI examples use bash. Set up a Linux CLI environment on Windows before proceeding.
- An existing block storage volume
Create the snapshot#
Verify the snapshot#
See also#
- How to schedule volume snapshots and restore data: cron or CI-driven snapshot schedules and restore drills
- Volumes console reference
- Create a volume
- Clone a volume
Usage Guidelines
The sample code, software libraries, command line tools, proofs of concept, templates, and other related technology on this page (including any of the foregoing that is provided by Quake AI personnel) is provided to you as Quake AI Content under the Quake AI Customer Agreement, or the relevant written agreement between you and Quake AI (whichever applies). Do not use this Quake AI Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the Quake AI Content (such as sample code) as appropriate for production grade use based on your specific quality control practices and standards. Deploying Quake AI Content may incur Quake AI charges for creating or using Quake AI chargeable resources, such as running Compute instances or storing data in Object Storage. Your use is also subject to the Acceptable Use Policy.
For the full policy, see Usage Guidelines.
Last validated: 01.09.2026
Quick answers
See Also
Volumes
Prerequisite
Block storage API error reference
Shares: Snapshots, Block Storage
How to emulate a branchable Postgres workflow
Shares: Snapshots, Volumes
How to schedule volume snapshots and restore data
Shares: Snapshots, Volumes
How to clone a block storage volume
Shares: Block Storage, Volumes