From 3ddd52ce4bab0f5cdf882b3f097d846db15ab965 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jo=C3=A3o=20Jandre?= Date: Fri, 15 Aug 2025 11:35:55 -0300 Subject: [PATCH 1/2] add doc about #9524 --- source/adminguide/virtual_machines.rst | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/source/adminguide/virtual_machines.rst b/source/adminguide/virtual_machines.rst index 786ec6d367..2b3dd79c82 100644 --- a/source/adminguide/virtual_machines.rst +++ b/source/adminguide/virtual_machines.rst @@ -1265,6 +1265,19 @@ When the snapshotting is complete, the Instance is thawed. You can use this functionality on Instances with raw block storages (E.g. Ceph/SolidFire/Linstor). +Disk-only File-based Storage Instance Snapshot on KVM +----------------------------------------------------- + +Since version 4.21, CloudStack supports incremental disk-only instance snapshots for VMs on KVM that are running on file-based storages (NFS, local, shared-mount-point). +Different from :ref:`Storage-based-Instance-Snapshots-on-KVM`, the VM is not frozen by default; only if the ``quiescevm`` parameter is informed. Furthermore, if ``quiescevm`` is true +the VM is only frozen during the operation of creating the deltas on the volumes of the VM, thus the downtime is minimal. + +When using this snapshot strategy, you will not be able to create volume snapshots, as these two features are not compatible. If you want to use both volume snapshots and instance snapshots +at the same time, you may inform the value ``KvmFileBasedStorageVmSnapshotStrategy`` on the ``vmSnapshot.strategies.exclude`` configuration, so that +this strategy is not used and the :ref:`Storage-based-Instance-Snapshots-on-KVM` feature is used instead. + +More information on this feature may be found in the `specification `_. + Limitations on Instance Snapshots --------------------------------- From b91e743b40d52d8f91c766076ab54a6f51870ff6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jo=C3=A3o=20Jandre?= <48719461+JoaoJandre@users.noreply.github.com> Date: Fri, 15 Aug 2025 11:43:13 -0300 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- source/adminguide/virtual_machines.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/adminguide/virtual_machines.rst b/source/adminguide/virtual_machines.rst index 2b3dd79c82..545e44d20a 100644 --- a/source/adminguide/virtual_machines.rst +++ b/source/adminguide/virtual_machines.rst @@ -1268,8 +1268,8 @@ You can use this functionality on Instances with raw block storages (E.g. Ceph/S Disk-only File-based Storage Instance Snapshot on KVM ----------------------------------------------------- -Since version 4.21, CloudStack supports incremental disk-only instance snapshots for VMs on KVM that are running on file-based storages (NFS, local, shared-mount-point). -Different from :ref:`Storage-based-Instance-Snapshots-on-KVM`, the VM is not frozen by default; only if the ``quiescevm`` parameter is informed. Furthermore, if ``quiescevm`` is true +Since version 4.21, CloudStack supports incremental disk-only instance snapshots for VMs on KVM that are running on file-based storages (NFS, local, shared mount point). +Different from :ref:`Storage-based-Instance-Snapshots-on-KVM`, the VM is not frozen by default; only if the ``quiescevm`` parameter is provided. Furthermore, if ``quiescevm`` is true the VM is only frozen during the operation of creating the deltas on the volumes of the VM, thus the downtime is minimal. When using this snapshot strategy, you will not be able to create volume snapshots, as these two features are not compatible. If you want to use both volume snapshots and instance snapshots