You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by an...@apache.org on 2020/05/06 20:12:53 UTC

[cloudstack-documentation] branch master updated: kvm-snapshot-explanation (#113)

This is an automated email from the ASF dual-hosted git repository.

andrijapanic pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git


The following commit(s) were added to refs/heads/master by this push:
     new e3a0683  kvm-snapshot-explanation (#113)
e3a0683 is described below

commit e3a06834d3700e166d212b02ad45d50a37fd9f8c
Author: Andrija Panic <45...@users.noreply.github.com>
AuthorDate: Wed May 6 22:12:44 2020 +0200

    kvm-snapshot-explanation (#113)
    
    * Update storage.rst
    
    * Update storage.rst
    
    * Update source/adminguide/storage.rst
    
    Co-authored-by: Nicolas Vazquez <ni...@gmail.com>
    
    * Update source/adminguide/storage.rst
    
    Co-authored-by: Nicolas Vazquez <ni...@gmail.com>
    
    Co-authored-by: Nicolas Vazquez <ni...@gmail.com>
---
 source/adminguide/storage.rst | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/source/adminguide/storage.rst b/source/adminguide/storage.rst
index 1254931..987dd5f 100644
--- a/source/adminguide/storage.rst
+++ b/source/adminguide/storage.rst
@@ -679,6 +679,21 @@ How to Snapshot a Volume
 
 #. Click the Snapshot button. |SnapshotButton.png|
 
+KVM volume Snapshot specifics
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+In recent CloudStack versions, by default, creating a volume snapshot for a running VM is disabled
+due to a possible volume corruption in certain cases. To enable creating a volume snapshots while the VM
+is running, the global setting 'kvm.snapshot.enabled' must be set to 'True'.
+
+The volume snapshot creation has changed in recent versions:
+
+Under the hood, first, a full VM snapshot is taken - this means that during the taking of
+the VM snapshot the VM will be in the "Paused" state (while RAM memory is being written to the
+QCOW2 file), which means that VM will be unavailable from the network point of view.
+When the VM snapshot is created, VM is unpaused/resumed, the single volume snapshot is exported
+to the Secondary Storage, and then the VM snapshots is removed from the VM.
+
 
 Automatic Snapshot Creation and Retention
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~