Skip to content

Commit e3a0683

Browse files
kvm-snapshot-explanation (#113)
* Update storage.rst * Update storage.rst * Update source/adminguide/storage.rst Co-authored-by: Nicolas Vazquez <nicovazquez90@gmail.com> * Update source/adminguide/storage.rst Co-authored-by: Nicolas Vazquez <nicovazquez90@gmail.com> Co-authored-by: Nicolas Vazquez <nicovazquez90@gmail.com>
1 parent b176803 commit e3a0683

1 file changed

Lines changed: 15 additions & 0 deletions

File tree

source/adminguide/storage.rst

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -679,6 +679,21 @@ How to Snapshot a Volume
679679

680680
#. Click the Snapshot button. |SnapshotButton.png|
681681

682+
KVM volume Snapshot specifics
683+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
684+
685+
In recent CloudStack versions, by default, creating a volume snapshot for a running VM is disabled
686+
due to a possible volume corruption in certain cases. To enable creating a volume snapshots while the VM
687+
is running, the global setting 'kvm.snapshot.enabled' must be set to 'True'.
688+
689+
The volume snapshot creation has changed in recent versions:
690+
691+
Under the hood, first, a full VM snapshot is taken - this means that during the taking of
692+
the VM snapshot the VM will be in the "Paused" state (while RAM memory is being written to the
693+
QCOW2 file), which means that VM will be unavailable from the network point of view.
694+
When the VM snapshot is created, VM is unpaused/resumed, the single volume snapshot is exported
695+
to the Secondary Storage, and then the VM snapshots is removed from the VM.
696+
682697

683698
Automatic Snapshot Creation and Retention
684699
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

0 commit comments

Comments
 (0)