Creating a volume backup – Support Guides

Learn how to create a backup of your Block Storage volume in the OVHcloud Control Panel.

If you value the data stored in your Block Storage volumes, it is worth organizing the backup of this data to prevent the potential impact of any issue on this data, whether it is a human error or a cluster incident.

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, the volume and volume snapshot might be unavailable. Volume snapshot creation does not require the volume to be detached from the instance.

A volume backup 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.

Both volume snapshot and volume backup allow you to:

Create backups of your volume with a few clicks and keep them for as long as you need.
Use the backups to restore your volume state.
Use the backups as a template to create identical volumes.

Requirements

Access to the OVHcloud Control Panel
A Block Storage volume created in your Public Cloud project

Creating a Backup

From the OVHcloud Control Panel:

Click Public Cloud in the top navigation bar.
Select your Public Cloud project.
Under Storage, click Block Storage.
In the row of the volume concerned, click the more options ... button and select Create a backup.

PCI_blockstorage_snapshot01**.png

It is not required to detach the volume from its instance first. However, if you wish to do so, please consult the Detaching a Volume section below.

On the next screen:

select the volume you wish to backup,
choose Volume Backup,
name your snapshot, and
click Create backup.

If your volume is attached to an instance, you will be prompted to detach it.

PCI_blockstorage_backup02*.png

The backup creation may take several hours, depending on the amount of data present on the volume, as well as the instance resource utilization and other host-specific factors.

We would also recommend that you perform your backups outside of your production hours.

Other best practices include:

Avoid creating snapshots and backups during peak hours.
Regularly validate that you can get your data back from your volume snapshot or volume backup.
Install the qemu-guest agent if it is not installed, or try to disable it if necessary.
Even if not mandatory, prefer to detach your volume when creating a volume snapshot.

Since a volume backup is a clone of the entire disk, it will have the maximum size of the original volume, regardless of the actual disk space allocation.

You will find the list of your volume backups by clicking Volume Backup under Storage in the left-hand navigation bar. As soon as the volume backup creation is requested, it will be added to this table.

Click the more options ... button to Delete or to Create a volume based on the respective volume backup. You can find information about creating a volume from a backup in this guide.

PCI_blockstorage_backup04*.png

Detaching a volume

If you wish to detach a volume from your instance, the best practice is to unmount the volume in the operating system before detaching it from the instance.

NOTE: An error message may appear if you have software or processes running on the additional disk. In this case, it is recommended to stop all processes before continuing.

Unmount the volume in the operating system

Establish an SSH connection to your instance, then use the command below to list the attached disks.

$ lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 254:0 0 10G 0 disk
└─sda1 254:1 0 10G 0 part /
sdb 8:0 0 10G 0 disk
└─sdb1 8:1 0 10G 0 part /mnt/disk

Unmount the partition using the command below: