Restore from backup
A restore lets you put a VM’s disks back the way they were when a recovery point was taken. You can roll the VM itself back, build a separate new VM from the recovery point, or turn one captured disk into a new volume. Only Replace Current VM changes the existing VM; the other two leave it untouched.
Which restore mode to choose
If you’re unsure, use Create New VM or Restore Selected Disk: they can’t damage the running VM.
How it works
- You pick a recovery point on the VM’s Backups tab and click Restore.
- You choose a mode, and the panel shows a Restore Preview and the Restore Impact.
- You click Confirm Restore. The VM shows Restoring while the disks are rebuilt from the backup copy.
- A message says “Recovery restore completed successfully” (or that it failed). Restored data volumes are attached but not mounted.
Before you begin
- A recovery point that succeeded. Queued, running or failed points can’t be restored.
- Write access to the workspace.
- For Replace Current VM: take a snapshot of the current state first, in case you need anything written since the backup.
- For Create New VM: credit for the new VM and its volumes, which are billed as new resources. The new VM is created in the same location as the original.
- No other restore, backup or resize running on the VM.
Restore in the portal
Replace Current VM can’t be undone. Files, database rows and settings changed after the recovery point are gone. Snapshot the VM first if there’s any chance you’ll need them.
Restore with the CLI or API
Find the recovery point ID with ibee vms backups list VM_ID, then restore:
--target-mode is replace (the default), new_vm or volume_only (with --selected-volume-id). The API call is POST /compute/cloud-vms/{vm_id}/backups/actions/restore with recovery_point_id and target_mode in the body; it returns a restore_id to poll at GET /compute/cloud-vm-backups/restores/{restore_id}. GPU VMs use ibee gpus backups and /compute/gpu-vms/....
Verify
Mount restored data volumes
Restored data volumes are attached but not mounted. Open the recovery point’s Details, click Copy commands under Mount Instructions, and run them inside the VM. They look like this:
Don’t format (mkfs) a restored volume: it already contains your data.
