Enable backups
Automated backups are copies of a VM’s disks that IBEE takes for you, every day or every week at a time you choose. Each copy becomes a recovery point you can restore from. It takes one switch in the portal; you can change the schedule or turn it off at any time.
When to use daily or weekly
Need a copy right now, before a risky change? Take a snapshot instead; it doesn’t wait for the schedule.
How it works
- You switch Automated Backups on. The first time, the schedule is saved straight away as Daily at 12:00 in your browser’s time zone.
- At each scheduled time, the backup starts within the following 30 minutes. It copies the root disk and every volume attached at that moment, while the VM keeps running.
- The first run is a full copy; the runs in the next 7 days store only changes; then a new full copy starts.
- Recovery points older than 7 days are deleted automatically, a weekly chain at a time.
Before you begin
- Write access to the VM’s workspace. Read-only members can see the schedule but not change it.
- Credit in your wallet: each recovery point is billed for the storage it uses. See Backup pricing.
- Attach every volume you want protected. Backups include all attached volumes and nothing else.
- Pick a quiet hour. The VM stays up, but its disks are busier while the copy runs.
Turn on backups in the portal
Switch Automated Backups on
Switch Automated Backups to Enabled. The first time, the portal saves a Daily schedule at 12:00 and shows “Backup enabled with default schedule (daily 12:00 …)”. If you turn backups back on later, the VM’s previous schedule is reused (“Backup re-enabled with existing policy”).
Turn on backups with the CLI or API
Enabling needs the backup storage price entry. List the backup storage plans, save one entry, then pass it to the CLI (the example uses jq to pick the entry; @FILE reads a file):
The API call is POST /compute/cloud-vms/{vm_id}/backups/enable with billing_catalog and schedule in the body; the price list is GET /compute/plans/backup-storage. Through the CLI or API, if you leave the schedule out, it defaults to daily at 20:00 UTC, not the portal’s 12:00; set timezone, hour and minute to be sure. The API also accepts hourly, a window_minutes of 5 to 180, and retention_days of 1 to 365. GPU VMs use ibee gpus backup-policy and /compute/gpu-vms/{vm_id}/backups/....
Verify
- The Backups tab shows Enabled with your schedule.
- After the next scheduled time (plus up to 30 minutes), a row appears under Recovery Points, with Topology such as Root + 1 data disk, a status, and its Storage size.
- Until then, the list says No recovery points yet.
For example, a Weekly + Sunday + 02:00 schedule saved on a Tuesday first runs the following Sunday between 02:00 and 02:30.
With the CLI, ibee vms backup-policy get VM_ID shows the schedule and next_run_at, and ibee vms backups list VM_ID lists the recovery points.
Turn backups off
Switch Automated Backups to Disabled. The portal shows “Backup schedule disabled”. No new backups are taken. Existing recovery points stay, can still be restored, and are billed until they expire or you delete them on Tools → Backups. Older weekly chains still expire after 7 days; the newest chain is kept until you delete it.
Deleting the VM also turns its schedule off and keeps its recovery points.
