Tools

VM snapshots

A snapshot is an on-demand recovery point captured from a running Cloud VM. Each snapshot includes the root disk and, optionally, attached data volumes. Snapshots are kept as a Recovery Point that you can restore in place, use to create a new VM, or roll back disk-by-disk.

Snapshots and automated backups share the same restore flow. Use snapshots when you want a recovery point at a specific moment — before a deploy, OS upgrade, or risky migration. Use backups for continuous, schedule-driven protection.

What’s captured

Every snapshot captures the root disk by default. You choose how much else to include via Capture Mode:

Capture ModeCaptures
Root volume onlyJust the boot disk. Attached data volumes are skipped.
All attached volumesRoot disk plus every attached persistent data volume.
Selective volumesRoot is always included; pick specific data volumes to add.

Restoring a snapshot set automatically reattaches captured data volumes to the target VM. Mount instructions for each data volume are surfaced in the Details drawer.

Restore options

When you click Restore on a snapshot recovery point, the same three modes are offered as backup restore:

ModeEffect
Replace Current VMRoll back the existing VM’s root disk and captured data disks in place.
Create New VMProvision a brand-new VM from the recovery point with new live block volumes.
Restore Selected DiskRoll back a single captured disk on the current VM.

See Restore a snapshot for full steps.

When to take a snapshot

  • Before a deploy or migration you might need to roll back.
  • Before an OS upgrade or kernel change.
  • To clone a known-good build into a new VM via the Create New VM restore mode.
  • As a manual checkpoint between scheduled backup runs.

For routine, ongoing protection, prefer scheduled automated backups.

Where to manage snapshots

Two surfaces in the IBEE Cloud portal manage snapshots:

SurfaceUse it for
Cloud VMs → <VM> → Snapshots tabRich per-VM flow: pick a Capture Mode (Root only / All attached / Selective), browse Recovery Points, and restore in three modes (Replace · Create New VM · Restore Selected Disk).
Tools → SnapshotsProject-wide catalog of block volume snapshots — point-in-time copies of your block volumes, with running totals (for example 1 · 50 GB total).

The project-level page is the aggregate view. It lists every snapshot with:

ColumnDescription
SnapshotName and short identifier you set when taking the snapshot.
Source VolumeVolume UUID the snapshot was taken from.
SizeSnapshot footprint (for example 50 GB).
StatusAvailable once the snapshot is ready to restore.
CreatedDate and time.
ActionPer-row menu (delete, copy ID, …).

A Take Snapshot button on the Tools page opens a simpler dialog:

  • Virtual Machine — pick a VM (running VMs are marked, e.g. test · 2 vCPU · 8 GB RAM · 50 GB disk · running).
  • Snapshot Name — required label.
  • Description — optional.
  • A reminder: For data consistency, run sync inside the server to flush pending writes before taking the snapshot.

Use the project-level dialog for ad-hoc, single-volume snapshots. Use the per-VM Snapshots tab when you need Capture Mode or guided restore options.

Quick start

  1. Open the VM detail page → Snapshots tab.
  2. Enter a Label (required) and an optional Description.
  3. Pick a Capture Mode — Root only, All attached, or Selective.
  4. (Selective only) Tick the data volumes to include.
  5. Click Create Snapshot. The recovery point appears in the Recovery Points list when complete.

See Create a snapshot for the full flow.

Recovery point list

Each row shows:

  • Snapshot — your label and the system-generated identifier (for example srp-20260509T162709Z).
  • Disks — what’s captured (Root + 1 data disk, 2 disk(s), …).
  • Created — date and time.
  • Storage — total recovery footprint.
  • Actions — Details, Restore, Delete.

Snapshots vs. backups

SnapshotsBackups
CadenceOn demandDaily or Weekly schedule
TriggerManual clickAutomatic
Capture modeRoot only · All attached · SelectiveAll attached (root + all data volumes)
Restore modesReplace · Create New VM · Restore Selected DiskSame
Best forPre-deploy checkpoints, ad-hoc rollback, cloningContinuous protection, DR

Most production VMs use both: scheduled backups as the safety net, manual snapshots before risky changes.