A volume snapshot is a recovery point stored within the same storage cluster as the original volume. Operations will be fast, but in case of an incident on the cluster, both volume and volume snapshot might be unavailable. Volume snapshot creation does not require the volume to be detached from the instance.
This is not to be confused with a volume backup which is an image created out of your volume, which is stored in the Object Storage cluster where the original volume is located. The level of resiliency is ideal and will allow you to quickly react to any incident on your volume, creating another volume from the backup. Volume backup creation requires the volume to be detached from the instance. For more information on this option, please consult this guide.
A snapshot of an additional volume serves two general purposes:
- You can create backups with a few clicks and keep them as long as needed.
- You can use the snapshot as a template for identical volumes.
This guide explains how to create a volume snapshot in the OVHcloud Control Panel.
Log in to the OVHcloud Control Panel, go to the
Public Cloud section, and select the Public Cloud project concerned. Then open
Block Storage in the left-hand navigation bar under Storage.
In the row of the volume concerned, click on
... and select
Create a backup (it is not required to detach the volume from its instance first). However, if you wish to detach your volume, please consult the "Detaching a Volume" section of this guide.
Note: If you have not already created a block storage backup, you can make one by following the instructions in this guide.
On the next screen, select
Volume Snapshot, name your backup, and then click
The snapshot creation time may take several hours, depending on the amount of data present on the volume, the instance resource utilization at the time of the snapshot, and other host-specific factors.
We therefore recommend that you perform your snapshots outside of your production hours.
Other best practices include:
- Avoid creating snapshots during peak hours.
- Install the qemu-guest agent if it is not installed... or try to disable it if necessary.
- Try not to "solicit" the server too much during the snapshot creation phase (I/O limitation, RAM consumption, etc.).
Since a volume snapshot is a clone of the entire disk, it will have the maximum size of the original volume, regardless of the actual disk space allocation.
Open the section
Volume Snapshot in the left-hand navigation bar. After the snapshot is created, it will be added to this table.
Click on the button
Delete a snapshot or to
Create a volume based on the respective snapshot. You can find further information in this guide.