Issues with creating a snapshot

[Andy_Welcomer]

Hello everyone,

We have a strange issue when attempting to create a snapshot in one of our regional environments. We have 4 VMs, 2 of them have mulitple VMDKs spread onto different datastores. When a snapshot is created, all the VMDKs (except for the first), seem to vanish. If you look at the properties of the VM, the path to the VMDKS points to the datastore where the primary VMDK is, and the file name is some random garbage. If the snapshot is deleted everything returns to normal. Has anyone ever seen this?

Thank you in advance.

Andy

[AnatolyVilchins]

Maybe this will help?:

http://communities.vmware.com/message/706956

iSCSI Software Support Department

http://www.starwindsoftware.com

[Andy_Welcomer]

Unforntatly it does't, but thank you for the reply.

Here is some more information. I just created a test machine with 7 VMDKs. 1 for the OS. and 6 others for data. All of the VMDKs are in seperate datastores. I take a snapshot of the machine, all of the 6 VMDKs loose their reference to the actual VMDK files. The all point to 64KB VMDK files in the datastore where the OS VMDK is located. These 64KB vmdks didn't exist until the snapshot was taken. When the snapshot is deleted, everything goes back to normal.

[vmroyale]

Hello.

"All snapshots are created in a default virtual machine directory. Even if the .vmdk disk file is located on different datastore than the virtual machine itself, delta files are created in the default virtual machine directory." - from kb 1002929.

This is the expected behavior. The reference is to the location of the snpashot file, which is in the default virtual machine directory.

Good Luck!