Skip to navigation

Custom images

A custom image is any starting point for a new VM other than an IBEE template: a snapshot you took of another VM, or a scheduled backup of another VM. It lets you copy a server you already set up, instead of installing everything again.

ISOs and your own disk images aren’t available. The ISOs tab on the Deploy page shows “No ISOs available for this account.” because the ISO service isn’t running, and there’s no way to upload a disk image you built elsewhere. Start from an OS image, then take a snapshot of the VM once it’s set up and use that for more copies. See ISOs.

When to use each source

SourceUse it forWhat the new VM getsLimits
SnapshotCloning a known-good server, for example a configured web server, to make more like itThe snapshot’s root disk; data volumes captured in the snapshot are restored and attached tooYou choose when it’s taken and which volumes it includes
BackupRebuilding a VM from last night’s automatic copyThe backup’s root disk only from the Deploy page (see the tip below)Only VMs with backups turned on have them
ISOAn operating system that isn’t in the templatesNot availableThe ISO service isn’t running, and an installer would also need the browser console, which is Coming soon

To restore a backup’s root disk and its data disks together, don’t use the Deploy page: open the original VM’s Backups tab, click Restore and choose Create New VM. See Restore from backup.

How it works

  1. On the Deploy page you switch Operating System from Templates to Snapshots or Backups and pick an item.
  2. IBEE copies the chosen disks to new disks for the new VM. The original VM and the snapshot or backup are not changed.
  3. The new VM boots with the copied disks. It gets its own new IP address and its own hostname.
  4. Data volumes that came with a snapshot are attached but not mounted; mount them inside the VM.

Before you begin

  • A snapshot or backup that has finished (status Available for snapshots, a successful run for backups). See Create a snapshot or Enable backups.
  • A plan whose root disk is at least as large as the snapshot’s or backup’s root disk. Disks can’t shrink.
  • Snapshots and backups can’t be copied to another location yet. Create the new VM in the same location as the original.

Create a VM from a custom image

1

Open the Deploy page

Open Infrastructure → Cloud VMs and click Deploy VM.

2

Pick the location and plan

Choose the Location of the original VM, then a Plan with a root disk at least as big as the original’s.

3

Pick the source

Under Operating System, switch to Snapshots or Backups and click the item you want. The Snapshots list shows each snapshot’s Snapshot, Source VM, Storage and Created values; Backups shows Backup, Source VM, Type and Created. The bottom bar shows your choice.

4

Finish and deploy

Continue with SSH Keys, Network Configuration, Billing and VM Details, then click Deploy. When you deploy from a snapshot, the portal shows “VM provisioning started. Restoring the captured root and data disks.” Restored data volumes get the original volume’s name plus -snapshot-restored-YYYYMMDD; you can rename them later in Block Storage.

5

Mount restored data volumes

If the snapshot included data volumes, they are attached to the new VM but not mounted. Open the snapshot’s Details on the original VM’s Snapshots tab and run the Mount Instructions inside the new VM. Don’t format them: they already contain your data.

Verify

When the new VM shows Running, sign in with the details under Overview → Connection Details and check that your files and services are there, for example with ls /var/www or systemctl status nginx. Run lsblk to see restored data volumes.

ISOs and your own disk images

Neither is available today:

  • ISOs. The portal has an ISOs page and an ISOs tab on the Deploy page, but the service behind them isn’t running: the tab shows “No ISOs available for this account.”, and choosing the tab without an ISO gives Please select an ISO. An ISO installer would also need the browser console, which is still Coming soon.
  • Your own disk image. There’s no upload or import for disk images built elsewhere, in the portal or the API.

To get a VM set up the way you want, create it from an OS image, install your software, take a snapshot, and create further VMs from that snapshot.

Limits

Value
Snapshot or backup locationSame location as the original VM
Root disk of the new planAt least the size of the captured root disk; 50 GB to 400 GB by plan
Data volumes from a snapshotRestored as new volumes and attached; billed as Block Storage
Data volumes from a backup (Deploy page)Not restored; use Create New VM on the Backups tab
ISOs and imported disk imagesNot available

Troubleshooting

You seeWhat it meansWhat to do
The snapshot or backup isn’t in the listIt’s still being created, it failed, or it belongs to another workspaceWait for it to finish, or check the original VM’s Snapshots or Backups tab.
Selected snapshot requires at least N GB root disk. Choose a plan with >= N GB. (or “Selected backup …”)The plan’s disk is smaller than the captured root diskPick a plan with a disk of at least N GB.
The new VM has no data volumesYou deployed from a backup on the Deploy page, which uses only the root diskUse Create New VM from the original VM’s Backups tab.
Data volume visible in lsblk but your files aren’t thereThe volume isn’t mountedRun the Mount Instructions. Don’t run mkfs.
The ISOs tab says “No ISOs available for this account.”, or Please select an ISOISOs aren’t availableUse Templates, Snapshots or Backups instead.