VM snapshots
A snapshot is a copy of a VM’s disks at one moment, taken when you ask for it. It’s like a save point in a game: before you upgrade the operating system or deploy a big change, you take a snapshot, and if things go wrong you go back to it. A snapshot can also be the starting point for new VMs that are copies of the original. Snapshots are kept until you delete them, and you pay for the storage they use.
When to use a snapshot
How it works
- You give the snapshot a name and choose a Capture Mode: which disks to include. The root disk is always included.
- IBEE copies the chosen disks at that moment. The VM keeps running.
- The snapshot appears as a recovery point on the VM’s Snapshots tab and on Tools → Snapshots.
- Later you can Restore it onto the same VM, into a new VM, or restore one disk.
Before you begin
- A Cloud VM or GPU VM, and write access to its workspace.
- Credit in your wallet: snapshot storage is billed per GB per month, for as long as the snapshot exists.
- For consistent data, stop writes before you snapshot: inside the VM run
sync, and stop or lock databases. IBEE doesn’t pause the VM’s filesystem, so a snapshot is like the disk after a sudden power cut (crash-consistent).
Key facts
Take a snapshot
See Create a snapshot for the details, including the Take Snapshot button on Tools → Snapshots.
Where to find snapshots
On Tools → Snapshots, each row shows Snapshot (name and ID), Disks, Storage, Status (Available when ready) and Created. Restores start from the VM’s Snapshots tab.
Use the API or CLI
Per-VM snapshots are in the public API. GPU VMs use /compute/gpu-vms/{vm_id}/snapshots, /compute/gpu-vm-snapshots/... and the CLI’s ibee gpus snapshots.
Taking a snapshot needs the snapshot storage price entry as billing_catalog: get it from GET /compute/plans/snapshot-storage?workspace_id=... and copy a selectable item’s billing_catalog.
Troubleshooting
Related pages
- Create a snapshot
- Restore a snapshot
- VM backups
- Custom images: create VMs from a snapshot
