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 want to revert to a snapshot. I noticed the following info in one of those files: ide0:1.fileName = "ROOT-11-000001.vmdk" So, if I were to revert to this snapshot, a new VMDK file would be created that would use ROOT-11-000001.vmdk as its parent. That makes sense. On Wed, Apr 23, 2014 at 11:32 PM, Mike Tutkowski < mike.tutkow...@solidfire.com> wrote: > Actually, I re-ran this scenario and this is what I observed: > > ROOT-1.vmdk > ^ > | > ROOT-1-000001.vmdk (Snapshot 1) > > I take another snapshot of the VM: > > ROOT-1.vmdk > ^ > | > ROOT-1-000001.vmdk (Snapshot 1) > ^ > | > ROOT-1-000002.vmdk (Snapshot 2) > > Let's say I revert to Snapshot 1. > > I see the following behavior: > > ROOT-1.vmdk > ^ > | > ROOT-2-000001.vmdk ROOT-2-000003.vmdk > > (ROOT-2-000001.vmdk and ROOT-2-000003.vmdk are children of ROOT-1.vmdk.) > > This brings up a couple questions: > > 1) If those two snapshots are siblings, then why in the GUI do I see that > one is listed as the parent of the other? > > 2) What happened to the data that was stored in ROOT-1-000002.vmdk? What > happens if I try to revert to Snapshot 2? That snapshot no longer appears > to be backed by a file on the datastore. > > Thanks! > > > On Wed, Apr 23, 2014 at 7:21 PM, Mike Tutkowski < > mike.tutkow...@solidfire.com> wrote: > >> 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 >> configuration for its root volume: >> >> ROOT-1.vmdk >> ^ >> | >> ROOT-1-000001.vmdk (Snapshot 1) >> >> I take another snapshot of the VM: >> >> ROOT-1.vmdk >> ^ >> | >> ROOT-1-000001.vmdk (Snapshot 1) >> ^ >> | >> ROOT-1-000002.vmdk (Snapshot 2) >> >> Let's say I revert to Snapshot 1. >> >> I see the following behavior: >> >> ROOT-1.vmdk >> ^ >> | >> ROOT-2-000002.vmdk (Snapshot 2) ROOT-2-000003.vmdk (Snapshot 1) >> >> From this, it appears both Snapshot 1 and Snapshot 2 have the same parent >> now. >> >> The only way I see this making sense is if the data in ROOT-1-000001.vmdk >> was merged into ROOT-1-000002.vmdk. >> >> Is this what happens in this situation? >> >> Thanks! >> >> -- >> *Mike Tutkowski* >> *Senior CloudStack Developer, SolidFire Inc.* >> e: mike.tutkow...@solidfire.com >> o: 303.746.7302 >> Advancing the way the world uses the >> cloud<http://solidfire.com/solution/overview/?video=play> >> *(tm)* >> > > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkow...@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the > cloud<http://solidfire.com/solution/overview/?video=play> > *(tm)* > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *(tm)*
