Skip to content

Commit 217a01d

Browse files
JoaoJandreJoão Jandre
andauthored
Update docs about volume snapshots on KVM (#423)
Co-authored-by: João Jandre <[email protected]>
1 parent 936bcf8 commit 217a01d

File tree

1 file changed

+13
-6
lines changed

1 file changed

+13
-6
lines changed

source/adminguide/storage.rst

Lines changed: 13 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1287,11 +1287,18 @@ is running, the global setting 'kvm.snapshot.enabled' must be set to 'True'.
12871287
12881288
The Volume Snapshot creation has changed in recent versions:
12891289
1290-
Under the hood, first, a full Instance Snapshot is taken - this means that during the taking of
1291-
the Instance Snapshot the Instance will be in the "Paused" state (while RAM memory is being written to the
1292-
QCOW2 file), which means that Instance will be unavailable from the Network point of view.
1293-
When the Instance Snapshot is created, Instance is unpaused/resumed, the single Volume Snapshot is exported
1294-
to the Secondary Storage, and then the Instance Snapshots is removed from the Instance.
1290+
When the VM is running, a disk-only VM snapshot is taken, exclusively for the volume in question.
1291+
If the VM is stopped, the volume will be converted (with qemu-img convert). The final storage location is
1292+
determined by the ``snapshot.backup.to.secondary`` configuration; if it is false the snapshot will be copied
1293+
to a different directory in the same primary storage as the volume; if it is true the snapshot will be copied
1294+
to the secondary storage. If the snapshot is being taken in a file-based storage (NFS, SharedMountPoint, Local),
1295+
it will be copied directly to its final storage location, according to the configuration.
1296+
1297+
Since 4.20.0.0, ACS supports incremental snapshots for the KVM hypervisor when using file-based storage (NFS, SharedMountPoint, Local),
1298+
to enable incremental snapshots the ``kvm.incremental.snapshot`` configuration must be enabled. Furthermore, in order to take incremental snapshots
1299+
the KVM host must have at least Libvirt version 7.6.0+ and qemu version 6.1+. The size of the snapshot chains
1300+
will be determined by the ``snapshot.delta.max`` configuration, which affects both KVM and XenServer snapshots.
1301+
More information on the incremental snapshot feature for KVM can be found in its `specification <https://github.com/apache/cloudstack/issues/8907>`_.
12951302
12961303
12971304
Automatic Snapshot Creation and Retention
@@ -1333,7 +1340,7 @@ incremental backups are supported, every N backup is a full backup.
13331340
+------------------------------+------------------+------------------+-----+
13341341
| | VMware vSphere | Citrix XenServer | KVM |
13351342
+==============================+==================+==================+=====+
1336-
| Support incremental backup | No | Yes | No |
1343+
| Support incremental backup | No | Yes | Yes |
13371344
+------------------------------+------------------+------------------+-----+
13381345
13391346
.. note::

0 commit comments

Comments
 (0)