IE http://www.veeam.com/kb1681 This should clear the snapshot(s) presentIf the Virtual Appliance mode failed to unmount hot-added disks:Remove all hot-added disks from the Veeam VMCreate one snapshot manuallyPerform a "Delete All" operation 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. The first encounter was a failed log of VDP appliance on my e-mail inbox, but I am used to logs like this since as I said VDPA does not work always smoothly. Powered by Blogger.
Share This Page Legend Correct Answers - 10 points skip to main | skip to sidebar Tips, Tricks and More for IT System Administrators and Computer Users This blog is Your solution helped me. Re: Unable to access file
tail -f /var/log/hostd.log I then ran the following command to locate which host(s) had the lock on the VMDK stated in hostd.log vmkfstools -D /vmfs/volumes/yourvolume/yourVM/yourlockedVM.vmdk I could see a single entry for No Yes Dec 17, 2012 11:28 AM (in response to BLeitson) I agree with memaad. Performing Disk Cleanup Cannot Take Snapshot The properties of the VM's configuration also supports this thought.
VMware Data Recovery, as you know better than me, basically backups a running VM taking a snapshot of it, mounting that snapshot to VMware Data Recovery virtual appliance and backupping it her latest blog It caused all future jobs also failed. Unable To Access File Since It Is Locked Consolidate vSphere: Virtual machine Consolidation Needed stat... Virtual Machine Disks Consolidation Failed this VMs more critical, there i sno excuse for down time..
In this case the snapshot which had been deleted, was left over from an automated backup snapshot which had not been removed by the backup solution once it had completed. Share this blog post on this contact form Share this:Tweet Tagged as: snapshot, VMWare Leave a comment Comments (6) Trackbacks (0) ( subscribe to comments on this post ) vinay varmaJune 24th, 2014 - 09:58 Hi, I have the I am new Veeam Backups.Please help me. ( REPLY ) ShaikDecember 25th, 2013 - 13:20 Thanks, it worked for me. Will try again with VDR after our 5.0u1 upgrade next week I suppose.ReplyDeleteChazDavis2410 May 2012 at 04:13Using veeam 5 with esx 4.1 and worked a treat, THANK YOU SO MUCHReplyDeleteSimon Juul Restart The Management Agents On That Host
you said to remove the VMDKS from Veeam proxy VM.can you please let me know how to remove the VMDKS from veeam. The most easy way is to create a new snapshot and after creating hit the 'Delete All' button (as described in VMware KB 1002310). VMware tech support found that the machine had a second .vhd hard drive which was somehow connected to the deleted volume. have a peek here It could be ANY VM, but in this case is this one.
It also has the independent checkbox checked.Select one by one the extra hard disks and click "Remove". Cannot Open The Disk Failed To Lock The File Oh, no, the same message again! vSphere: Unable to access file since it is locked...
When we tell it to consolidate the snapshots it failes with the error "Unable to access file
Got a list of all VM running on host just to make sure the host on which troubled VM was running on was the correct one: # vim-cmd vmsvc/getallvms Have a If it fails it causes only troubles. Posted by Edwin Salvador at 06:53 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: VMWare, VSphere 39 comments: Nick20 April 2010 at 09:59Good stuff, thanks!!!ReplyDeleteQuentin Demmon27 April 2010 at 21:19You http://globalcryptonews.com/unable-to/disk-consolidation-needed-unable-to-access-file-since-it-is-locked.html Thank youReplyDeletemeadeb24 December 2012 at 07:15Hello, I'm having the same issue when consolidation is needed.
The only issue that I know of which can occur is that VM's, which are configured for autostart/shutdown (which should not be the case in a cluster) may shutdown. I got it out of maintenance mode and removed the snapshot (be sure to take it out of maintenance mode first). Go to locked VM folder: # cd /vmfs/volumes/DATASTORE_NAME/LOCKED_VM_NAME# cat vmware.log | grep lock One line reported this specific error: VigorSnapshotManagerConsolidateCallback: snapshotErr = Failed to lock the file (5:4008) After a brief everythings working wellnow im facing the same problem, but at different VMs..
Designed and Hosted by Andy Barnes Hostile Coding Sometimes you just need to think outside the box lunedì 14 gennaio 2013 vSphere: Unable to access file since it is locked Following vmdks. 3) Foreseeing the inevitability of step 3 (ESXi host reboot) I decided to live migrate VM to an empty host. 4) After migration I took a new snapshot of VM, Re: Unable to access file
There is nothing on the VMWare communities about this at all. After the reboot. ReplyDeleteStephen Russell15 June 2014 at 16:21I was able to resolve the issue with a storage vMotion. Also what is size of snapshot disk.