reredok
asked on
VMWARE
Hi Experts,
actual I clean up an old ESX 3.5 Environment i.e. delete old snapshots.
Maybe caused by much ESX overload, within the second Deletion I obtain a timeout error.
In snapshotmanager there are no further snapshots but in vmfs file system on esx host i determine some curios files:
/vmfs/volumes/<id>/vmware- server-nam e-nnnnn-de lta.vmdk
where nnnnn is an ongoing number
How can i delete snapshots finally?
THX
actual I clean up an old ESX 3.5 Environment i.e. delete old snapshots.
Maybe caused by much ESX overload, within the second Deletion I obtain a timeout error.
In snapshotmanager there are no further snapshots but in vmfs file system on esx host i determine some curios files:
/vmfs/volumes/<id>/vmware-
where nnnnn is an ongoing number
How can i delete snapshots finally?
THX
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
that looks like a 13gb snap you're trying to commit. I'd go home and check it again in the morning :)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I have had this on several occastions and vmware support suggested to do a V2V using vConverter since deleting large snapshots has a high failure rate
ASKER
V2V a virtual machine in a "virtual" machine?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
After waiting hours ... ;-) no change :-((
Inside a experimental VM with same -delta Problem, I establish a new Snapshot. New big Files were created:
W3KTS02-000003-delta.vmdk
W3KTS02-000004-delta.vmdk ...
Then I've shutdown VM and after getting some curious errors in VMware Infrastructure-Client, I wasn't able to start VM until this morning.
So restart is complete and *magic* all -delta-File were deleted :-)
Actually I'll test this concept on other problem-vm's
Inside a experimental VM with same -delta Problem, I establish a new Snapshot. New big Files were created:
W3KTS02-000003-delta.vmdk
W3KTS02-000004-delta.vmdk ...
Then I've shutdown VM and after getting some curious errors in VMware Infrastructure-Client, I wasn't able to start VM until this morning.
So restart is complete and *magic* all -delta-File were deleted :-)
Actually I'll test this concept on other problem-vm's
If the virtual machine isn't running when you are deleting snapshots then the process will be quicker as ESX doesn't have to cope with handling new changes whilst commiting/deleting old changes.
ASKER
ominous: (see image)
=======
vmware1.jpg