...
To create a snapshot of a volume, root or otherwise, first list the volumes in the cloud with
| Code Block |
|---|
openstack volume list |
Then, to create a snapshot of one of the volumes, do do
| Code Block |
|---|
openstack volume snapshot create [--force] --volume <volume> <snapshot_name> |
...
Single VM
To backup a single VM, whether image-backed or volume-backed, it is recommended to create a snapshot of the root volume of the VM, as shown instance as shown above. A full backup is also recommended for volume-backed instances when the original volume is not guaranteed to be preserved.
...
To backup a single VM and it's attached volumes, one must create a snapshot or backup of the VM first, including the root volume of the VM as well as disk if the instance is volume-backed, and then perform a snapshot or backup of all other attached volumes separately.
...
The network configuration and security groups of VMs are not recorded when performing an snapshot or backup of the root volume of the VM. If this information needs to be backed up in order to reconfigure the VM after restoration, we recommend storing these values in a file. These can be done as before when storing the full configuration of a VM, e.g. in YAML format, with
...
Shared File Services (SFS) cannot be backed up as they are distributed storage solutions that do not live in the same cloud. The recommended way to backup a VM with a SFS is to unmount the SFS before performing the snapshot or or backup of the VM, in order to avoid possible corruption, and remounting it afterwards. This can be easily done, with admin privileges, with
...