Skip to navigation

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

ScheduleRecovery points you can go back toChoose it when
DailyAbout one per day, for 7 to 14 daysThe VM changes every day: databases, user uploads, production apps
WeeklyAbout one per week, for 7 to 14 daysThe VM rarely changes, or cost matters more than a recent copy

Need a copy right now, before a risky change? Take a snapshot instead; it doesn’t wait for the schedule.

How it works

  1. 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.
  2. 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.
  3. The first run is a full copy; the runs in the next 7 days store only changes; then a new full copy starts.
  4. 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

1

Open Backups

Open the VM (Infrastructure → Cloud VMs or GPU VMs) and click the Backups tab.

2

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”).

3

Pick the frequency

Under Schedule backups, choose Daily or Weekly.

4

Pick the day (Weekly only)

Under On, choose a day from Sunday to Saturday.

5

Pick the time

Under At, choose an hour from 00:00 to 23:00. Times are in your browser’s time zone, and the schedule is saved with that time zone. If your users are in another time zone, convert first.

6

Save

Click Save Schedule. The button shows Saving…, then a message confirms the schedule, for example “Backup config saved: weekly on Sunday at 02:00 …”.

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):

ibee -o json compute backup-storage-plans \
| jq '[.items[] | select(.selectable)][0].billing_catalog' > backup-sku.json
ibee vms backup-policy enable VM_ID \
--billing-catalog @backup-sku.json \
--schedule '{"frequency": "daily", "hour": 2, "minute": 0, "timezone": "Asia/Kolkata"}'

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

  1. The Backups tab shows Enabled with your schedule.
  2. 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.
  3. 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.

Limits

PortalAPI and CLI
FrequencyDaily or WeeklyHourly, Daily or Weekly
Start timeOn the hour, 00:00–23:00, then within 30 minutesAny hour and minute, then within window_minutes (5–180, default 30)
Retention7 days1 to 365 days (default 7)
Full backupEvery 7 days, incremental in betweenEvery 1 to 30 days (default 7)
What’s copiedRoot disk + all attached volumesSame
Backups running at once1 per VMSame

Troubleshooting

You seeWhat it meansWhat to do
Backup enable failedThe schedule couldn’t be savedReload and try again. Check your billing state under Billing.
Backup schedule save failedThe new schedule wasn’t savedTry again; your previous schedule still applies.
The switch is greyed outA restore from a backup is runningWait for the restore to finish.
There’s no switch, only Enabled or DisabledYou have read-only accessAsk a workspace admin for write access.
No recovery point after the scheduled timeThe run is still queued, or it failedWait 30 minutes. Then check Activity logs.
”Backup policy is disabled for this VM. Enable backups before creating a backup run.”You asked for a backup now while backups are offTurn backups on first.
A new volume isn’t in the recovery pointIt was attached after the run startedIt’s included from the next run.