You know, the more I think about how VMware implemented this, the more it
becomes clear what's going on under the hood.
The -flat and -delta files contain the data and their corresponding VMDK
files contain metadata like who your parent, if any, is.
Then the VMSN files come into play when you wan
Actually, I re-ran this scenario and this is what I observed:
ROOT-1.vmdk
^
|
ROOT-1-01.vmdk (Snapshot 1)
I take another snapshot of the VM:
ROOT-1.vmdk
^
|
ROOT-1-01.vmdk (Snapshot 1)
^
|
ROOT-1-02.vmdk (Snapshot 2)
Let's say I revert to Snapshot 1.
I see t
Hi,
I was working again with VMware snapshots today to test this functionality
against CloudStack's managed storage.
I have a question that perhaps one of you can answer:
Let's say I have a root volume called ROOT-1.vmdk.
I take a snapshot of the applicable VM, which produces the following
conf
