Skip to content

Volume Snapshots Console

Reference · Updated Sep 2026

Coming from another cloud?

▸AWS·EBS Snapshots

EBS Snapshotshigh

  • 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.
AWS docs ↗
▸Azure·Snapshots

Snapshotshigh

  • 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.
Azure docs ↗
▸DigitalOcean·Volume Snapshots

Volume Snapshotshigh

  • 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.
DigitalOcean docs ↗
▸Google Cloud·Standard/Archive Snapshots

Standard/Archive Snapshotshigh

  • 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.
Google Cloud docs ↗
▸Hetzner·N/A (No equivalent)

N/A (No equivalent)high

  • No support for volume snapshots in API or console; explicitly stated 'we do not provide Backups or Snapshots for Volumes' and server snapshots exclude volumes.
  • Workarounds like rsync/dd to new volume required, unlike Cinder's create/delete/get/manage_snapshot API.
  • Recent confirmations (2026) show no addition of feature.
  • Created as Image type='snapshot' via server action; stored under /images.
Hetzner docs ↗

Volume snapshots console

Overview#

Select Storage > Volume Snapshots to view the volume snapshots console. The console displays a list of volume snapshots available in your project.

Volume Snapshots console showing an empty list with columns ID/Name, Size, Status, Volume ID/Name, Created At, and ActionClick to zoom
Volume Snapshots console (empty state)

Columns#

The volume snapshots list shows these columns, in order:

  • ID/Name: the snapshot identifier and display name.
  • Size: the snapshot size in GiB.
  • Status: the current snapshot state.
  • Volume ID/Name: the identifier and name of the source volume.
  • Created At: the snapshot creation timestamp.
  • Action: per-row controls for the snapshot.

Select a snapshot to view snapshot details. You can view snapshot specifications and messages related to volume snapshot operations.

Actions#

You can take the following actions on snapshots.

  • Edit
  • Backup
  • Delete
  • Create a volume using the snapshot as a template
  • Launch an instance using the snapshot as the source for the bootable volume

See also#

Was this page helpful?