Link to home
Start Free TrialLog in
Avatar of fpifferini
fpifferiniFlag for Switzerland

asked on

no snapshot with VMware ESX 3.5 connected to iSCSI

I've a VMware ESX server (version 3.5.0, 123630) connected with an external iSCSI storage, the Datastore of my virtual machines are on the iSCSI storage.
When i try ti make a snapshot of a VM, apparentely this is done, but when I try to revert or change snapshot image point, in fact, no snapshot is present.
Strange is also that is "very fast" to make the apparent snapshot.

Some one experience the same problem and can help me debug it?

Thank you
Avatar of markzz
markzz

As we don't use iSCSI in production due to the potential IO limitations, I've not see this issue and can only make comment of where I would start to look for some answers.
When you initiate a snapshot of the VM via the VC or VI Clienttry to watch the VMFS file system where your guest lives, can you see it build any deltas?
Also look in the VC, Administraton radio button and look at the system logs.
Avatar of Paul Solovyovsky
Is the disk setup as an independent disk?
Avatar of fpifferini

ASKER

I've to say that if I keep the default flag on "Snapshot the virtual machine's memory" I got the error message "Failed to take a memory snapshot, since the virtual machine is configured with independent disks".
The snapshot is proceeding only if I remove the flag (but this is a fake, in reality no snapshot is done).

If I browse the Datastore, I can see that the delta file .vmdk is not created!
Usually with a snapshot should be created a delta of the disk named <vmname>-0001.vmdk and a snapshot of the memory in a file named <vmname>-Snapshot1.vmsn

From the VI client I don't see any special error message log.

If I've the VM on the local storage of the server (not on the iSCSI), snapshots are working well fine.

ASKER CERTIFIED SOLUTION
Avatar of Paul Solovyovsky
Paul Solovyovsky
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
The issue was related to the settings of Indipendent disk.
Changed it, now problem is fixed.
Thank you to all.