Hi,
How did you create the snapshot?
As you posted in the API/code section, did you create it via code?
If you want to know if it damaged your VM we need to know more..
A filelist to start with.
--
Wil
Hi,
sorry but I posted it in the wrong section.
I created it via UI. That is why I was surprised that VMWare did not complain.
The original snapshot was a cold one, i.e. the VM was turned off. The new snapshot was "hot", i.e. with VM up and running.
Once I received the error message that it was not possibile to delete the first snapshot, it disappeared from the UI. In order to check if there was a naming clash I renamed the duplicated snapshot but the first is missing in any case. Basically in the following snapshot screen there should be one at the beginning called A-BOSD, then the intermediate, then the 3rd still called A-BOSD (which is the one that I then renamed into A-BSOD2).
Given the issue, I shutted down the VM, copied it onto another disc, restarted it, and in any case it is apparently working. Then I shutted it down again. That been said, how do you want the filelist to be supplied?
Humm.. OK.. in that case there is nothing to worry about.
You can have snapshots with the same name.
See, I just created two "blub" snapshots a few minutes ago.
They show up just fine with the vmrun API:
$ vmrun -T fusion listsnapshots /Users/wil/Virtual\ Machines.localized/Win10TP/Win10TP.vmx
Total snapshots: 5
Before installing beep
After fresh boop
blub
blub
Yeep
and the accompanying .vmsd file snippet on my VM looks fine to me too (cut down to only show the relevant part)
snapshot3.uid = "20"
snapshot3.filename = "Win10TP-Snapshot20.vmsn"
snapshot3.parent = "18"
snapshot3.displayName = "blub"
snapshot3.createTimeHigh = "374422"
snapshot3.createTimeLow = "-1229136199"
snapshot3.numDisks = "1"
snapshot3.disk0.fileName = "Win10TP-system-000004.vmdk"
snapshot3.disk0.node = "scsi0:0"
snapshot.mru3.uid = "19"
snapshot4.uid = "21"
snapshot4.filename = "Win10TP-Snapshot21.vmsn"
snapshot4.parent = "20"
snapshot4.displayName = "blub"
snapshot4.createTimeHigh = "374422"
snapshot4.createTimeLow = "-1221038999"
snapshot4.numDisks = "1"
snapshot4.disk0.fileName = "Win10TP-system-000002.vmdk"
snapshot4.disk0.node = "scsi0:0"
As the latter part is the only place that the displayName is set, I am not seeing any issues by doing this.
Note sure why the snapshot would have disappeared, that would be part of the riddle.
If you have a snapshot .vmdk not represented in the .vmsd file then you would indeed have a missing snapshot in the chain.
You can attach filelist (and contents such as a .vmsd file) via a zip file (I hope... you never know with this shitty new forum what you can attach or not)
--
Wil
Hi,
Pretty sure that you're not missing data.
If you would miss data then your virtual disk would be corrupted and you would either:
- not being able to boot the VM
- have your guest OS complain about disk corruption issues
I suppose that for an extra test you could run a disk check over your virtual disks. If the guest OS does not report an error then you're safe in regards to lost data.
All snapshots are chained together. If a snapshot goes missing from the user interface then it is always a mismatch in the .vmsd file. The .vmsd file is what is being used to show the snapshot screen and built up the snapshot tree on there.
The virtual disk itself and its snapshots are in a chain and if the chain is broken you can no longer boot the vm.
It is possible to have snapshots that do not show up in the snapshot tree.
If that's the case then normally you can get rid of those by first deleting all snapshots for your VM. Then create a new snapshot, wait until it is done and immediately delete the snapshot afterwards. Most of the times that gets rid of stray snapshots.
re. different version.
Sorry, I forgot that you used VMware Workstation, my snapshot dialog screenshot is from VMware Fusion.
It does not matter though as both products work exactly the same in this regard.
There is no difference except for the screens.
Even at low level it works the same (and I'm sure about that as it is important for me to know for the backup software that I write on how this works)
edit: back to your filelist
You have files that look like:
ORADATA-000001-s001.vmdk <-- first snapshot, first disk slice
ORADATA-000001-s002.vmdk <-- first snapshot, second disk slice
ORADATA-000002-s001.vmdk <-- second snapshot, first disk slice
ORADATA-000002-s002.vmdk <-- second snapshot, second disk slice
ORADATA-000003-s001.vmdk <-- third snapshot, first slice
ORADATA-000003-s002.vmdk <-- third snapshot, second slice
ORADATA-s001.vmdk <-- base disk, first slice
ORADATA-s002.vmdk <-- base disk, second slice
So once you remove all snapshots in the snapshot dialog there should be no more ORADATA-00000x-s001.vmdk files.
Also the snapshot dialog should show as many snapshots are there are unique snapshot files.
Note that the numbers do not have to be incremental.
another edit: I forgot to answer one question. No a cold snapshot does not have a .vmsn file, so it is normal for it to not be there.
Hope that helps,
--
Wil