​
Overview

A snapshot is a point-in-time copy of one volume. It’s the cheapest rollback available and the starting point for cloning a disk’s contents.
Navigation: Storage → Snapshots. Titled Snapshots, subtitled “Manage volume snapshots and backups”.
There’s no create button here — snapshots are created from the volume. Use Create Snapshot on a row in Volumes.

​
Columns

Snapshot Name, Type, State, Size, and Created are sortable. Expanding a row shows Volume, Zone, Account, Size, and Created.

​
Manual versus scheduled

The Type column tells you who made the snapshot:
Filter Type to Manual to find snapshots a person deliberately took — those are usually the ones worth keeping. Scheduled snapshots are pruned by their policy’s retention; manual ones are never pruned automatically and accumulate until you delete them.

​
States

The table shows these values exactly as the platform reports them, so you’ll see BackedUp and BackingUp run together, while the State filter presents the same values as Backed Up and Backing Up. Same states, different spacing.

​
Filtering

​
What you can build from a snapshot

This is the useful part. A BackedUp snapshot gives you three forward paths plus a download.
Revert Snapshot depends on a platform revertable flag as well as the state, so it won’t appear for every completed snapshot. Where it’s absent, use Create Volume and swap the volumes over instead — same outcome, non-destructive.

​
Creating a volume from a snapshot

The dialog summarises the source Snapshot and its Zone. Success reports “Volume creation started successfully”.

​
Reverting

Reverting overwrites the source volume. The dialog is blunt about it:
  • All data written after this snapshot was taken will be lost
  • The volume will be restored to its state at snapshot time
  • This action cannot be undone
If the current contents might matter, take a fresh snapshot first — then you can revert the revert.

​
Downloading

Download Snapshot doesn’t hand you a file directly. It starts an extraction job and reports “Snapshot extraction started successfully”; the image becomes available when that job completes. Watch Jobs.

​
Worked example: clone a disk to test a migration

You want to test a schema migration against real data without touching production.
1

Snapshot the production data volume

From Volumes, Create Snapshot on the volume. Name it for its purpose: prod-data-premigration-test.
2

Wait for BackedUp

Creating and BackingUp aren’t usable yet. Sort by Created to find it quickly.
3

Create a volume from it

Create Volume → name it test-data-clone, and attach it to your test machine in the same step.
4

Run the migration against the clone

Production is untouched. The clone is a full independent copy.
5

Delete the clone and the snapshot when done

Both consume storage quota. The clone is a full-size volume, not a thin reference.
For a rollback point before a risky change, a snapshot is the right tool — fast to take, fast to revert. For protection against losing the machine entirely, use Backups: snapshots live alongside your volumes, backups are held separately.

​
Deleting

The dialog reads: “Deleting snapshot "" will permanently remove all data. This action cannot be undone.”
Deleting a snapshot policy does not delete the snapshots it created — they stay and keep consuming quota. If you retire a policy, come back here and clean up its output, filtering Type to the policy’s interval to find them.

​
Empty and error states

A “no snapshots match your filters” state exists in the code but can never display, due to a contradictory condition. Filtering to nothing shows an empty table rather than an explanation — so if the table looks blank, check whether a filter is active.

Volumes

Where snapshots are created.

Snapshot Policies

Automate them, with retention.

Backups

Whole-machine protection, held separately.

Templates

Turn a snapshot into a reusable image.