ESXI REMOVE ALL SNAPSHOTS HANGS AT 99%

Check and make sure that the process is actually stuck and not just taking a very long time.
To do this, follow these steps:
1. Make sure SSH service is running on the ESXi host
Navigate to configuration -> security profile -> services -> Click on Propertiesesxi-services
Choose the ‘SSH’ service, ‘Options’, and click ‘Start’
esxi-ssh
Once SSH is enabled, connect to the ESXi host using your favorite ssh client.
2. Run -> vim-cmd vmsvc/getallvms
getallvms
Find the vmid of the virtual machine, in this case its 20.
3. Now run -> vim-cmd vmsvc/get.tasklist 20<- this is the # of the vm from above
gettasklist
4. Find the removeallsnapshots task # then run:
vim-cmd vimsvc/task_info 185720854 <-this # will be different for you
If you see:  “The object has already been deleted or has not been completely created” or similar, your snapshot removal is probably frozen, but in order to be sure, let’s look at the file sizes and make sure nothing is changing.
5. cd into the datastore where the vm is located.
The path is /vmfs/volumes/datastore-name/vm-name
(NOTE: tab-complete is your friend)
vmfs
6. Now Run ->  watch -d 'ls -lut | grep -E "delta|flat|sesparse"'
before-vpxa
Take notice on the file sizes and make sure they stay the same. If they are changing, the snapshot removal process is still working and I would just wait it out. Don’t risk data loss!
7. If the data file sizes doesn’t change for a long time ( 1-2 hours, just to be safe)
Restart the vpxa service on the ESXi host.
Configuration -> security profile -> services -> properties -> vpxa ->options ->restartNote: You will lose connectivity with the host from vCenter, just reconnect after a minute.
8. Go back to the SSH terminal and re-run the command:
watch -d 'ls -lut | grep -E "delta|flat|sesparse"'
after-vpxa
You will eventually see the delta files disappear, and will be able to power on your vm with no snapshots present ! ðŸ™‚
___________________________________________________________________________________________

Comments

Post a Comment

Popular posts from this blog

Siem architecture

What is SIEM?   Security Information and Event Management solutions are a combination of the formerly disparate product categories of SIM (security information management) and SEM   (security event management). SIEM technology provides real-time analysis of security alerts generated by network hardware and applications. The objective: To help companies respond to attacks faster and organize mountains of log data. Security Information and Event Management (SIEM) technologies take part in a crucial role in addressing the compliance, efficiency, and security needs of an enterprise. The central part of SIEM technologies is the ability to collect security data from all the critical assets on a network and present that data as actionable information via a single interface. SIEM solutions come as software, appliances, or managed services. Increasingly, SIEM solutions are being used to log security data and generate reports for compliance purposes.     SIEM Solution    SIEM intelligenc
Read more

SharesFacebookTwitterGoogle+PinterestEmailSumoMe VMware ESX – “Unable to access a file since it is locked

Image
After transferring and/or trying to restart a VM in ESX you may be presented with the error message “Unable to access a file since it is locked”. Now what you need to do is work out what is actually locking this file and then (unsurprisingly) find a way to unlock it. Generally the problem will be caused by one of three things. 1.  Process Lock:  There is a process on the ESX server that still has hold of a file(s) used by the VM.  This is one of the most common causes.  To resolve this there have been a couple of good VMware Forum postings  here  and  here  that have been consolidated to  this useful posting over  at  GabesVirtualWorld.com   (*Note: It is worth checking out the comment by Kent at the bottom of the posting).  Also, check out Tecumseh’s posting  here . 2.  Disk Naming Conflict:  Two or more disks with the same VMDK name. This can be caused by another disk with the same VMDK file name being referenced by the VM.  This may have occurred due to a VM move where the
Read more