Snapshots
Capture point-in-time snapshots of your virtual machine state for backup, testing, and rapid recovery.
Overview
A snapshot captures the complete state of a virtual machine at a specific point in time, including all disk contents and the VM configuration. Snapshots are stored alongside the VM and can be used to revert the machine to a previous state in seconds.
Snapshots are ideal as a safety net before performing risky operations such as software upgrades, configuration changes, or OS patches. They are not intended as a long-term backup solution — for scheduled backups and offsite replication, see the Backups & DR section.
Snapshot limit per VM
A virtual machine can hold up to 32 snapshots at once — the limit imposed by the underlying virtualisation platform. In practice we strongly recommend keeping no more than 2 to 3 active snapshots per VM.
Each additional snapshot increases storage consumption (snapshots grow with every disk write since they were taken), slows down disk I/O, and makes consolidation operations longer and riskier. Long-lived snapshot chains are one of the most common causes of degraded VM performance and stuck deletes.
Creating a Snapshot
To create a snapshot of a virtual machine:
- Navigate to the VM detail page by selecting the device from Virtual Datacenter > All Devices.
- Open the Snapshots tab.
- Click Create a new Snapshot.
- Enter a name for the snapshot (e.g., "Before kernel upgrade" or "Clean install baseline").
- Optionally enter a description to provide additional context.
- Click Create Snapshot to begin the snapshot process.
For the most consistent snapshot, shut down the VM (or quiesce the guest filesystem yourself from inside the VM) before creating the snapshot. The snapshot is taken without quiescing the guest or capturing memory state, so a running VM's snapshot is crash-consistent only and may capture in-flight disk writes that require filesystem recovery after a revert.
Snapshot creation time depends on the size of the VM's disks. The VM remains accessible during the snapshot process.
Viewing Snapshots
All snapshots for a VM are listed in the Snapshots tab on the VM detail page. Snapshots are displayed in a hierarchical tree structure showing parent-child relationships. Each entry displays:
- Snapshot Name — The label you assigned when creating the snapshot. The current active snapshot is highlighted with a "You are here" indicator.
- Description — The optional description text provided during creation.
- Created At — The date and time the snapshot was taken.
- Size (MB) — The storage consumed by the snapshot in megabytes.
Editing a Snapshot
You can update the name and description of an existing snapshot without affecting its captured state. From the snapshot list on the VM's Snapshots tab, click the pencil (edit) icon next to the snapshot, update the fields in the dialog, and save. This is useful for clarifying snapshot context or adding details after the fact.
Restoring a Snapshot
Restoring a snapshot discards all changes made to the VM since the snapshot was taken. This includes any files written, configurations changed, and software installed after the snapshot point. This action cannot be undone.
To restore a VM to a previous snapshot:
- Navigate to the VM's Snapshots tab.
- Locate the target snapshot in the list.
- Click Restore next to the snapshot.
- In the confirmation dialog, check the acknowledgement checkbox confirming that all disk data since the snapshot will be permanently deleted.
- Click Restore Snapshot to proceed.
A restore reverts the VM to the exact state captured in the snapshot, including the power state at the time the snapshot was taken. If the snapshot was taken while the VM was powered off, start the VM manually afterwards; a snapshot taken on a running VM is restored to a running state. Restore duration depends on the underlying virtualisation platform and is typically a few seconds.
Cloning a Device from a Snapshot
You can create a new virtual machine by cloning from an existing snapshot. This feature is available for Linux, Windows, and ISO-based devices.
- Navigate to the VM detail page and open the Snapshots tab.
- Locate the snapshot you want to clone from and click the clone icon. A popover confirms the action: "Clone device from a snapshot".
- In the Clone device from a snapshot modal, fill in the following fields:
- Organization — Select the target organization (this field is only shown for reseller tenants).
- Device name — Enter a name for the new device.
- Hostname — Enter the hostname for the new device.
- Create from snapshot — Select the snapshot to use. The dropdown lists "Current device state" along with all available snapshots (showing name and date).
- NIC network selection — Choose a network and configure IP fields for each network interface.
- Deploy device without network — Optionally check this box to create the device without any network interface (Linux devices only).
- Click Clone to create the new device.
Deleting a Snapshot
Snapshots consume storage space. Delete snapshots you no longer need to free up resources:
- Navigate to the VM's Snapshots tab.
- Click the delete icon (trash) next to the snapshot you want to remove.
- Check the confirmation checkbox acknowledging that the deletion is irreversible.
- Choose whether to delete only the selected snapshot or the snapshot and all its children.
- Click Save changes to proceed.
Deleting a snapshot does not affect the current state of the VM. Only the stored snapshot data is removed. Note that snapshot deletion takes time and depends on the snapshot size.
Best Practices
- Snapshot before changes — Always create a snapshot before applying OS updates, software upgrades, or configuration changes. This gives you a fast rollback path.
- Use descriptive names — Name your snapshots with the date and context (e.g., "2024-03-15 Pre-migration") so you can quickly identify the right one to revert to.
- Limit snapshot count — Each snapshot consumes storage proportional to the changes since the last snapshot, and additional snapshots slow disk I/O. The platform allows up to 32 snapshots per VM, but we recommend keeping no more than 2–3 active at a time.
- Do not use as primary backup — Snapshots are stored on the same infrastructure as the VM. For disaster recovery, configure scheduled backups that replicate data to a separate location.
- Clean up regularly — Review your snapshots periodically and delete those that are no longer needed. A weekly review cadence is recommended for active workloads.