ahmad1467
asked on
Removing VM Snap Shots
I am running VMware 4.0 and I was trying to delete a Snap shot in snapshot Manager but it seems like it’s taken a little longer to finish. It seems like it’s been at 95% for about an hour, when I view the job in my vSphere Client under task it shows that the job is in progress, does this seem normal? But meanwhile the server is down and I don’t have the option to turn it on, is there something I should try or should I continue waiting?
Thanks
Thanks
How big is the snap?
ASKER
I had more than one so I was going to delete them one by one, it looks like it might have been a snapshot that was created by Symantec.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The Down side is this is my Exchange server so email is down now, if it’s taken to long is there a way to cancel the possess so that I can turn the VM back on? I tried right clicking on the task but canceled is grayed out.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
hi,
when committing snapshots the problem is that it requires more disk space. this is something that is well explained in the following articles:
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1002836
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1015180
so if you do not have enough disk space the "remove snapshots" function will fail always !!! No matter what you do. In these cases then the best solution is to clone the source VM to another datastore and test it. If not I would suggest to remove snapshots manually by using the CLI.
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1002310&sliceId=1&docTypeID=DT_KB_1_1&dialogID=166065714&stateId=0%200%20166063563
I believe that this snapshot is too large and that you do not have enough disk space to commit it.
when committing snapshots the problem is that it requires more disk space. this is something that is well explained in the following articles:
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1002836
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1015180
so if you do not have enough disk space the "remove snapshots" function will fail always !!! No matter what you do. In these cases then the best solution is to clone the source VM to another datastore and test it. If not I would suggest to remove snapshots manually by using the CLI.
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1002310&sliceId=1&docTypeID=DT_KB_1_1&dialogID=166065714&stateId=0%200%20166063563
I believe that this snapshot is too large and that you do not have enough disk space to commit it.
Do you have remaining space on the datastore?
ASKER
Thanks for all the help and information, the removal did complete later that evening. The Snapshots were created when Symantec Backup Exec Jobs fail and left the snapshot behind.
Yep...as suspected. That happens with my VM b/u software (Veeam) on occasion, as well. Lately it's been good tho. Glad it completed for you...
Regards,
~coolsport00
Regards,
~coolsport00