Add disks and back up your VM

Add and grow disks from the Storage tab, and take and restore backups from the Backups tab.

Updated 6 November 2026

Adding a disk

On the VM's Storage tab, press Add disk and choose a size and a storage pool. Disks start at 5 GB, a VM can have up to 8 extra ones, and they count against your tier's disk limit.

The easy way: fill in Mount at, such as /data, and choose ext4 or xfs. Cloud formats the disk and mounts it for you, and adds it to fstab in a way that won't stop your VM from booting if the disk ever goes missing. The VM has to be running and have the guest agent, and you can't use a system folder like /etc.

By hand: leave Mount at empty, and the disk shows up blank. Find it by its ID, since these stay the same when device names don't:

ls -l /dev/disk/by-id/

Windows VMs see a blank disk, which you format and give a letter in Disk Management.

Growing a disk

Press Grow. Disks can only grow, never shrink. Think about that before going big, because the extra space counts against your limit for good.

  • A disk Cloud formatted is grown inside the system for you when it can reach it.
  • The OS disk usually grows its filesystem on the next boot, so restart after growing it.
  • A disk you formatted yourself needs growing by hand, inside the system.

Removing a disk

Press Delete. Its data is destroyed. If Cloud mounted it, Cloud unmounts it first, and refuses if something's still using it. If you added it to fstab yourself, take that line out first, or the next boot may fail.

The OS disk can't be removed.

Backing up

On the Backups tab, press Back up now. It's a snapshot, so the VM keeps running, although it can't take other changes until it finishes. The tab shows how it's going.

Backups are something you start yourself. Don't assume you have one unless you can see it listed.

Restoring

Restoring replaces everything on the VM with the backup. Anything newer is gone.

  1. On the Backups tab, press Restore on the one you want.
  2. Choose whether to start the VM afterwards.
  3. Type RESTORE to confirm.

The VM stops and is restored over. Its network is put back as it is now, so its address and ports keep working, and its firewall rules are checked. PuTTY may warn you about a new host key afterwards.

If a restore fails, the VM is left in a failed state, so open a ticket.

Keep your own copies

Backups are a convenience, not a promise. Cloud is a beta on shared hardware, with no guarantee against losing a VM, and deleting a VM deletes its backups too. For anything that matters, keep a copy somewhere else as well. rsync to another machine or an outside storage service both work well.