Skip to navigation

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

You want to…ModeOverwrites the current VM?
Undo a bad deploy or an accidental delete, on the same VMReplace Current VMYes. Everything written after the recovery point is lost.
Look at old data, test a restore, or clone a server, without touching the originalCreate New VMNo
Get back the files on one disk onlyRestore Selected DiskNo: you get a new, detached volume

If you’re unsure, use Create New VM or Restore Selected Disk: they can’t damage the running VM.

How it works

  1. You pick a recovery point on the VM’s Backups tab and click Restore.
  2. You choose a mode, and the panel shows a Restore Preview and the Restore Impact.
  3. You click Confirm Restore. The VM shows Restoring while the disks are rebuilt from the backup copy.
  4. 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

1

Open the recovery point

Open the VM, click the Backups tab, and scroll to Recovery Points. Click Details to see the captured disks, their sizes and the Mount Instructions.

2

Start the restore

Click Restore on the recovery point. A side panel opens with three modes.

3

Choose a mode and fill it in

ModeWhat to fill in
Replace Current VMNothing else
Create New VMNew VM Name (a name is suggested), New VM Plan (plans are marked Eligible, Disk too small or Unavailable), and Restored Data Volume Names for each data disk
Restore Selected DiskThe Captured Disk to restore. The preview says, for example, “This will create a new detached volume from testblockstorage (vdc).”
4

Read the impact

ModeRestore Impact says
Replace Current VM”The current VM will be stopped, its root disk will be replaced, and captured data disks will be attached again.”
Create New VM”A new VM and new live block volumes will be created from this recovery point and billed as active resources.”
Restore Selected Disk”The selected disk will be restored as a detached volume. You can attach it later without changing the current VM.”
5

Confirm

Click Confirm Restore. Wait for “Recovery restore completed successfully”.

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:

# Build a new VM from the recovery point, leaving the original alone
ibee vms backups restore VM_ID --recovery-point-id RECOVERY_POINT_ID \
--target-mode new_vm --target-vm-name web-01-restored --target-plan-id PLAN_ID --yes
# Check progress
ibee vms backups restore-status RESTORE_ID

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

ModeCheck
Replace Current VMThe VM is Running again with the same IP address and hostname. Sign in and check that the files are as they were at the recovery point.
Create New VMA new VM appears in the list with its own new IP address. Sign in and check your data, then point DNS at it if you’re switching over.
Restore Selected DiskA new, detached volume appears in Block Storage. Attach it to a VM and mount it.

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:

sudo mkdir -p /mnt/data
sudo mount /dev/vdc /mnt/data
echo 'UUID=<filesystem-uuid> /mnt/data ext4 defaults,nofail 0 2' | sudo tee -a /etc/fstab

Don’t format (mkfs) a restored volume: it already contains your data.

Limits

Value
Recovery points you can restoreSucceeded ones, kept for 7 days (up to about 14 days)
Location of a new VMSame as the original VM
New VM’s root diskAt least the captured root disk’s size
Restores at a time1 per VM
CostNo charge for the restore itself; a new VM and new volumes are billed as usual

Troubleshooting

You seeWhat it meansWhat to do
Only successful backups can be restoredThe recovery point is queued, running or failedPick a recovery point that succeeded.
A recovery restore is already in progress. Please wait.Another restore is running on this VMWait for it to finish.
”Backup is being restored or deleted; try again later”The recovery point is busyTry again after the other operation ends.
A plan is marked Disk too smallIts root disk is smaller than the captured onePick a bigger plan.
A plan is marked Unavailable”This plan is not available in this location.”Pick another plan.
Recovery restore failedThe restore stopped with an errorCheck Activity logs, then retry or contact support.
A data volume is in lsblk but your files aren’t visibleThe volume isn’t mountedRun the Mount Instructions.