Of all the posts I read this is the only one that worked! Please type your message and try again. 11 Replies Latest reply: Dec 17, 2012 11:28 AM by a.p. Sometimes a VM, is locked in a Snapshot state, and the only way forward is to 1. Kinda annoying, but it worked. Source
Post più recente Post più vecchio Home page Iscriviti a: Commenti sul post (Atom) Cerca nel blog Caricamento in corso... Latest Blog Posts Veeam CBT Data is Invalid - Reset CBT Without Powering Off VM View 7 Administrator Blank Error Dialog/Window After Upgrade App-V 5.x Writing to the native registry vSphere The properties of the VM's configuration also supports this thought. 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
I hate VMware support procedures and times.Don't worry, I solved it by myself, and let me tell you how:1) Shutdown the VDR appliance. Primary Sidebar Widget Area Recent Posts Baby announcements… to a geek "Apache Directory Studio" hangs at 14% when connecting to an LDAP server HPE OneView 2.0.7: “Unable to retrieve asset tag Join Now For immediate help use Live now! So, following KB: Investigating virtual machine file locks on ESXi/ESX I logged in to ESXi host on which my VM was running.
Show 11 replies 1. on vSphere ESXi upgrade is really slow (About to install…)Aurelien PONCINI on vSphere ESXi upgrade is really slow (About to install…)moi on vSphere ESXi upgrade is really slow (About to install…)Florent Since then I tried to create another snapshot to make sure that the VM-consolidator helper shows in the snapshot manager so that I can commit it. Performing Disk Cleanup Cannot Take Snapshot I got it out of maintenance mode and removed the snapshot (be sure to take it out of maintenance mode first).
ReplyDeleteSertec6 June 2013 at 02:01I´ve done all this but I still get.../sbin/fsck.xfs: LABEL = data12 does not existFSK faild for at least one filesystemNow what?? Epic win.ReplyDeleteSteven7 April 2011 at 03:45WOW Thanks very much! The most easy way is to create a new snapshot and after creating hit the 'Delete All' button (as described in VMware KB 1002310). It will free up the locked files in your VMs that were not sucessfuly backed up.2) Create manually a snapshot in every VM with the problem, then "Delete all" snapshots will
I had an issue like this, none of the obvious solutions from veeam or vmware would work.. Detected An Invalid Snapshot Configuration Thank You! 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 Sorry, we couldn't post your feedback right now, please try again later.
The problem is that the virtual machine was crashing every time that I've tried to consolidate and wasn't able to finish without the error: Unable to access file
thanks GOD finally i found this blog.i ever had similliar problem, i try same steps that you describe above and DONE. http://webinweb.net/unable-to/vmware-remove-snapshot-unable-to-access-file.html So, the only thing which i did is Powered Off virtual servers and restart ESX machine and error resolved.ReplyDeleteTheDemographic6 January 2012 at 14:32Yep...I had only 1 HDD...deleted it (not remove from Reply ↓ Stephen on 11/06/2014 at 17:13 said: Thanks very much for the post, logged a call with vmware and they could not fix this issue. if im delete the Extra vDisk at VDR, i there restart needed or not at the VDR Appliance or the VMs that the vDisk Locked. Restart The Management Agents On That Host
Like Show 0 Likes (0) Actions Go to original post Actions Remove from profile Feature on your profile More Like This Retrieving data ... Have you tried 1. Re: Unable to access file
Basicly the guest was powered off and locked. Vmware Manually Delete Snapshot Files Take a look at the settings of your VM, select the hard drive and check if the file is a snapshot and not the original vmdk. Thank you!!!
If you are experiencing a similar issue, please ask a related question Suggested Solutions Title # Comments Views Activity SolarWind and DNS Server 12 51 30d pass through and VGPU 6 DELETE ALL the Snapshots....WAIT and be Patient. It also has the independent checkbox checked.Select one by one the extra hard disks and click "Remove". An Error Occurred While Consolidating Disks: Could Not Open/create Change Tracking File. Thank youReplyDeleteHarryjames18 January 2013 at 22:15restrhttp://www.veeam.com/kb1213ReplyDeleteMohammed Ali2 April 2013 at 21:47u r a star .... 100% works for me ReplyDeletebunk3 April 2013 at 11:21Good stuff.
Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES Services Overview Subscribe for updates: Products Contacts License Management Company Products Resources Veeam University Partners Success Stories Contact Veeam sales Buy Veeam products Renewals Online shop License Management Support Technical Documentation Knowledge Base but which file ???? Power back on the host and simply remove the guest from inventory.
If you make a mistake, just hit Cancel and do it again.5) Verify that you have the single and right hard disk in place.6) Power on the (VMware Data Recovery) appliance. Still says file is locked.