Updated Branches: refs/heads/master b2b8f0e9f -> e23d6b2af
CLOUDSTACK-1561. Docs. Update VM Snapshots section. Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/e23d6b2a Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/e23d6b2a Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/e23d6b2a Branch: refs/heads/master Commit: e23d6b2af414a5789800a5b848f1a527dfdf66ce Parents: b2b8f0e Author: Jessica Tomechak <[email protected]> Authored: Mon Apr 22 23:07:29 2013 -0700 Committer: Jessica Tomechak <[email protected]> Committed: Mon Apr 22 23:08:10 2013 -0700 ---------------------------------------------------------------------- docs/en-US/vm-snapshots.xml | 10 ++++++---- 1 files changed, 6 insertions(+), 4 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/cloudstack/blob/e23d6b2a/docs/en-US/vm-snapshots.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/vm-snapshots.xml b/docs/en-US/vm-snapshots.xml index 8d4bcf9..3e72fe4 100644 --- a/docs/en-US/vm-snapshots.xml +++ b/docs/en-US/vm-snapshots.xml @@ -24,8 +24,8 @@ <section id="vm-snapshots"> <title>Virtual Machine Snapshots for VMware</title> <para>(VMware hosts only) - In addition to the existing &PRODUCT; ability to snapshot VM volumes, - you can now take a VM snapshot to preserve all of the VM's state and data. + In addition to the existing &PRODUCT; ability to snapshot individual VM volumes, + you can now take a VM snapshot to preserve all the VM's data volumes as well as (optionally) its CPU/memory state. This is useful for quick restore of a VM. For example, you can snapshot a VM, then make changes such as software upgrades. If anything goes wrong, simply restore the VM to its previous state using the previously saved VM snapshot. @@ -51,7 +51,9 @@ <listitem><para>If a VM has some stored snapshots, you can't attach new volume to the VM or delete any existing volumes. If you change the volumes on the VM, it would become impossible to restore the VM snapshot - which was created with the previous volume structure.</para></listitem> + which was created with the previous volume structure. + If you want to attach a volume to such a VM, first delete its snapshots. + </para></listitem> <listitem><para>VM snapshots which include both data volumes and memory can't be kept if you change the VM's service offering. Any existing VM snapshots of this type will be discarded.</para></listitem> <listitem> @@ -72,7 +74,7 @@ <section id="vm-snapshot-configure"> <title>Configuring VM Snapshots</title> <para>The cloud administrator can use global configuration variables to control the behavior of VM snapshots. - To set these variables, go through the Global Settings are of the UI.</para> + To set these variables, go through the Global Settings area of the &PRODUCT; UI.</para> <informaltable> <tgroup cols="2" align="left" colsep="1" rowsep="1"> <thead>
