Rob van Hamersveld.nl My digital life

26Apr/126

VMware “Unable to access file since it is locked” when removing snapshot

Today I ran into a problem with a VM which have snapshots but are  not visible in the VMware snapshot manager. As you can see in the screenshot vCenter reports no snapshots;

But when I took a look at the datastore folder of this VM in noticed several delta vmdk files which indicates there are active snapshots. The properties of the VM's configuration also supports this thought.

So how to fix this? The most easy way is to create a new snapshot and after creating hit the 'Delete All' button (as described in VMware KB 1002310). After I did this a new error pops up; "Unable to access file <unspecified filename> since it is locked".

Why is it locked? Well, you can find out by following the instructions in VMware KB 10051 but I my case it was simple. The customer is using snapshots for backups by Veeam Backup and Replication, so the only one who's making snapshots is the Veeam VM. The specific job which responsible for the problem VM was crashed and that's why the base VMDK of the problem VM was still locked by the Veeam VM. After disconnecting the VMDK from the Veeam VM I was able to create a new snapshot and hit the "Delete All" button to commit the delta-vmdks.

Comments (6) Trackbacks (0)
  1. Hi, I have the same problem. you said to remove the VMDKS from Veeam proxy VM.can you please let me know how to remove the VMDKS from veeam. I am new Veeam Backups.Please help me.

  2. Thanks, it worked for me. In my environment there are 6 VMs has same issue, summary tab shows consolidate is required, but when i run consolidate it’s give me same error “Unable to access file since it is locked” But i tried with different ways first i tried as above said, but no luck, what i did is migrate the VM which is giving problem to another Host and created snapshot example “1234” then after that i select delete all button to clear all snapshots, It’s deleted all snaphots and finally it work fine.

    Thanks,

  3. Thnak you very much, This happened to me once before but I forgot about the mounted discs on the VEEAM proxy vm. After I removed them I was able to “Delete ALL” snapshots for the exchange VM and everything was good.

  4. restarting the management service and create a test snapshot delete all should work , or create a snapshot and restarting d management agents also should work

  5. thanks this save me

  6. thanks this save me hours of digging. In my case it was Avamar holding the vmdk, but same reason.


Leave a Reply

No trackbacks yet.