Snapshots provide a way to get point-in-time recovery for your instance. In a typical usage example you would snapshot your instance before applying patches. Once the patches are installed, if your tests are not satisfying or an incompatibility is introduced, you can revert to the snapshot and restore the previous working state.

Snapshots are strongly tied to your instance: if you delete your VM, they will be deleted too.

Snapshots are located in the instance detail screen

Create a new Snapshot


While it is not required, it is strongly advised to stop a Compute instance before creating a snapshot of its storage volume in order to ensure all data is written to the disk controller so it reaches the underlying hypervisor backend storage. Alternatively, using the facility provided by your OS to flush cached writes to disk ensures data recently written will be snapshotted. On Linux, this can be achieved with the sync(1) command.

It is recommended to avoid performing any action on the related instance during a snapshot operation to ensure unintended side-effects leading to operation failure.

From the instance detail screen, click on Create Snapshot to create a new snapshot. A successfully created snapshot has a green check-mark on his left.

Wait for a snapshot to be ready before operating on it

Revert to a Snapshot

To revert a snapshot your machine has to be stopped. From the snapshots list, in the instance detail, click on the Revert button on the line of the snapshot you wish to revert.

Using the exo CLI, the equivalent command is exo compute instance snapshot revert.

Delete a Snapshot

In the instance details view, select the snapshot you want to delete and click on the Delete button to delete it.

Using the exo CLI, the equivalent command is exo compute instance snapshot delete.

Export/Download a Snapshot

It is possible to export the snapshot of a volume: once exported, the snapshot file can be downloaded either for backup purposes, or used as input to create a new Custom Template.

To export a snapshot, use the following exo CLI command:

$ exo compute instance snapshot export ce295d39-421e-49c4-81f7-9890c3db3600
 ✔ Exporting snapshot ce295d39-421e-49c4-81f7-9890c3db3600... 4s
│ URL      │ │
│ Checksum │ 34ef65cad47428e799f9bc6c02b7ebd5                                 │

Using the CLI’s templated text output format, it is possible to download an exported snapshot disk file locally, for example as an extra backup method:

$ wget -O ce295d39-421e-49c4-81f7-9890c3db3600.template \
    $(exo compute instance snapshot export ce295d39-421e-49c4-81f7-9890c3db3600 --output-template {{.URL}} 2>/dev/null)
--2021-09-17 10:51:12--
Resolving (
Connecting to (||:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10301276160 (9.6G) [application/binary]
Saving to: ‘ce295d39-421e-49c4-81f7-9890c3db3600.template’


The duration of a snapshot operation may vary greatly depending on the size of your volume and the amount of data stored on it. The entire operation can take up to several hours, during which no other operation should be performed on the instance.

Once exported, the returned pre-signed URL will only be valid for 6 hours. You can get a new one by repeating the operation, knowing that the subsequent exports of an already exported snapshot will be instantaneous.


  • Snapshots are limited to 30 per account. Please contact support should you need more.
  • Only one snapshot operation is permitted at a time. For example, when a snapshot is being destroyed, you cannot create a new snapshot of the same storage volume.
  • Snapshots cannot be named at the moment, they are identified by a UUID.
  • When you delete an instance, its snapshots are deleted too.
  • Snapshots are currently unavailable for Storage Optimized instances.