Skip to content

Commit b7c8ca8

Browse files
Merge pull request apache#64 from apache/vm-snapshot-doc-update
vm snapshots tags and corrections
2 parents 002e998 + 75459f7 commit b7c8ca8

1 file changed

Lines changed: 15 additions & 16 deletions

File tree

source/adminguide/virtual_machines.rst

Lines changed: 15 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -416,7 +416,7 @@ To delete an affinity group:
416416
Virtual Machine Snapshots
417417
-------------------------
418418

419-
(Supported on VMware and XenServer)
419+
(Supported on VMware, XenServer and KVM (NFS only))
420420

421421
In addition to the existing CloudStack ability to snapshot individual VM
422422
volumes, you can take a VM snapshot to preserve all the VM's data
@@ -441,6 +441,13 @@ create a long chain of these parent/child snapshots, which amount to a
441441
"redo" record leading from the current state of the VM back to the
442442
original.
443443

444+
After VM snapshots are created, they can be tagged with a key/value pair,
445+
like many other resources in CloudStack.
446+
447+
KVM supports VM snapshots when using NFS shared storage. If raw block storage
448+
is used (i.e. Ceph), then VM snapshots are not possible, since there is no possibility
449+
to write RAM memory content anywhere.
450+
444451
If you need more information about VM snapshots on VMware, check out the
445452
VMware documentation and the VMware Knowledge Base, especially
446453
`Understanding virtual machine snapshots
@@ -475,22 +482,14 @@ The cloud administrator can use global configuration variables to
475482
control the behavior of VM snapshots. To set these variables, go through
476483
the Global Settings area of the CloudStack UI.
477484

478-
Configuration Setting Name
479-
480-
Description
481-
482-
vmsnapshots.max
483-
484-
The maximum number of VM snapshots that can be saved for any given
485-
virtual machine in the cloud. The total possible number of VM snapshots
486-
in the cloud is (number of VMs) \* vmsnapshots.max. If the number of
487-
snapshots for any VM ever hits the maximum, the older ones are removed
488-
by the snapshot expunge job.
489-
490-
vmsnapshot.create.wait
485+
.. cssclass:: table-striped table-bordered table-hover
491486

492-
Number of seconds to wait for a snapshot job to succeed before declaring
493-
failure and issuing an error.
487+
====================== ========================
488+
Configuration Description Type
489+
====================== ========================
490+
vmsnapshots.max The maximum number of VM snapshots that can be saved for any given virtual machine in the cloud. The total possible number of VM snapshots in the cloud is (number of VMs) \* vmsnapshots.max. If the number of snapshots for any VM ever hits the maximum, the older ones are removed by the snapshot expunge job
491+
vmsnapshot.create.wait Number of seconds to wait for a snapshot job to succeed before declaring failure and issuing an error.
492+
====================== ========================
494493

495494

496495
Using VM Snapshots

0 commit comments

Comments
 (0)