VM backups
A backup is an automatic copy of a VM’s disks that IBEE takes on a schedule you choose, daily or weekly. Each copy is called a recovery point. If the VM breaks, or someone deletes important files, you can put a recovery point back onto the VM, build a new VM from it, or restore a single disk. Backups are off until you turn them on for each VM, and they cost extra: you pay for the storage the recovery points use.
When to use backups
Most production VMs use both: scheduled backups as the safety net, and a snapshot before each risky change.
How it works
- You turn on Automated Backups on the VM’s Backups tab and pick a schedule.
- At the scheduled time (within 30 minutes after it), IBEE copies the root disk and every volume attached at that moment. The VM keeps running.
- The first copy is a full backup. For the next 7 days, copies are incremental: they store only what changed. Then a new full backup starts the next 7-day chain.
- Each copy is stored separately from the VM’s own disks and appears as a recovery point.
- Old recovery points are deleted automatically after 7 days, a whole weekly chain at a time.
Before you begin
- A Cloud VM or GPU VM, and write access to its workspace.
- Credit in your wallet: backup storage is billed per GB per month.
- Data that must be consistent (databases) is best protected by stopping writes or using the database’s own dump tool before the backup time. IBEE copies the disks without pausing the VM’s filesystem, so a backup is like the disk after a sudden power cut.
Key facts
Turn on backups
See Enable backups for every option.
Where to find backups
The VM’s Recovery Points list shows:
Until the first backup runs, the list says No recovery points yet.
Restore options
Restore is available on successful recovery points:
See Restore from backup.
Remote backup in another data centre
If you need copies kept outside the data centre where your VM runs, IBEE offers remote backup to a separate data centre as a managed service. It isn’t turned on from the portal: the IBEE team sets it up on request and shares the details and pricing for your setup. Contact sales@ibee.ai to arrange it.
Use the API or CLI
Per-VM backups are in the public API. GPU VMs use the same paths under /compute/gpu-vms/{vm_id} and /compute/gpu-vm-backups, and the CLI’s ibee gpus group.
The two list calls return only finished, successful runs. To see a queued, running or failed run, read it by ID with GET /compute/cloud-vm-backups/runs/{run_id}. For a scheduled run, the last_status field of the backup policy shows how the latest finished run ended.
Enabling backups and taking one now need the backup storage price entry as billing_catalog. Get it from GET /compute/plans/backup-storage?workspace_id=... and copy a selectable item’s billing_catalog. Through the API, the schedule can also be hourly, and retention_days can be 1 to 365. Convert to Snapshot is portal-only.
