Backups are scheduled, automated recovery points for Cloud VMs. When enabled on a VM, IBEE captures the root disk and all attached persistent data volumes on a recurring schedule and retains the resulting Backup Recovery Points so you can restore a VM in place or roll forward to a new VM.
If you want a one-off recovery point you trigger manually, use Snapshots instead. Backups and snapshots use the same restore flow but differ in cadence: backups run on a schedule, snapshots run on demand.
Each backup recovery point captures:
The captured topology, total recovery storage size, and creation timestamp are visible on each recovery point.
Two surfaces in the IBEE Cloud portal:
The project-level Backups page (under Tools → Backups) shows columns:
A Search names and UUIDs… box filters the catalog; column headers toggle sort order.
If no VMs in the project have backups enabled, the page shows an empty state: No Backups — Automatic backups are an optional service that creates daily snapshots of your VPS instance for a small additional fee. Enable backups on individual servers to see them here. A Manage Servers → button takes you to Cloud VMs so you can pick a VM and turn on its schedule.
Backups are configured per VM under Backups → Automated Backups. See Enable backups for the full schedule options.
Quick view of the schedule controls:
Changes save automatically — the Saving… indicator confirms the schedule is being persisted.
Once at least one backup has run, recovery points appear in the Backup Recovery Points list with:
srp-20260509T162709Z).Until the first backup runs, the panel reads “No backups available yet — backups will appear here once the schedule captures the VM storage set.”
When you click Restore on a recovery point, three modes are offered (mirroring the snapshot restore flow):
See Restore from backup for full restore steps.
Backup storage is billed separately from the VM. See Backup pricing for the rate and example calculations.
Most production VMs benefit from both: scheduled backups for routine protection, plus a manual snapshot before risky changes.