Like mentioned before the VM is powered off and the file lock message pops up when trying to delete the snapshots. The base disk was simply still connected to the backup proxy VM, and for that reason the base disk was locked aka the snapshot could not be consolidated (as the base power down VM 2. Si te fijas en los settings de la VM, en los discos, verás que apuntas a los discos de snapshot que son ficheros con el nombre de la máquina virtual como http://webinweb.net/virtual-machine/vmware-unable-to-consolidate-file-is-locked.html
Removal of Snapshots - fix VM snapshot Given the situation that the VM can be powered on without issues, new snapshots can be created but not deleted, something strange is going 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 This is the ESXi server which has the lock on the VMDK file. Next locate which ESXi host has a network adaptor with that MAC address. Re: Virtual machine disks consolidation is needed y Unable to Access file
As always before performing anything; check, double check, test and always ensure you have a backup. Thank you! One is to run a vMotion/svMotion in VMware to another host.
I guessed that the VDP appliance was root of the problem, so I shut it down and tried to delete all the snapshots of the problematic VM. Running ESXi 5.0u1. I wanted to make sure that is how you did it before I proceed. Virtual Machine Disks Consolidation Is Needed No Snapshots If there is an issue during this process, it is possible for further snapshots to be unable to consolidate, causing removal failures.You receive warnings that the snapshot removal process failed because
Kill 1053523 Now that the lock was removed I was able to re-run the Consolidate Snapshots and it ran successfully. Disk Consolidation Needed - Unable To Access File Since It Is Locked 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 Don’t have an account? From there I ran a search for "lock".
Search for: Posts Calendar October 2015 M T W T F S S « Aug Nov » 1234 567891011 12131415161718 19202122232425 262728293031 Recent Posts New Date for VMware’s GO Consolidate Virtual Machine Disk Files Stuck The delta files follow the directory, but now you can successfully Snapshot -> Consolidate, and the delta files will go away. And my luck was, that selecting "consolidate" ended in that one brilliant error: Unable to access file since it is locked. Allan says: March 7, 2013 at 18:21 Erik, So you shut down the server first, manually removed the base disks (backup disks), ran the consolidate, added back the original server vmdk
Voila, I was near the solution, since the virtual disks consolidated into one disk and the VM properties disk file linked to the right vmdk file. run consolidate 4. Virtual Machine Disks Consolidation Failed Saludes on The Odyssey of building a ligh…E. An Error Occurred While Consolidating Disks: 5 (input/output Error). Unfortunately the VM can be "powered on", "powered off" and no locked file can be found.
This might happen under the hood but it doesn't work the same way when it is a physical server. this contact form Every day there is a scheduled job that backup differentially all the VMs in our organization. Waiting on a downtime approval would take too long. The next step was to restart the management agents on the ESXi host. Nothing major, or so I thought. An Error Occurred While Consolidating Disks Could Not Open/create Change Tracking File
Register. Pressing the "Consolidate" button did not solved the problem neither. It seemed that the problem is bigger than I first thought. Re: Virtual machine disks consolidation is needed y Unable to Access file
At this point it looked as it the consolidation was going to work but at about 20% it failed. Restart The Management Agents On That Host A VMware-level snapshot was made, the base disk was hot-added to the VM that handles the backup. Bookmark the permalink.
Si todo está correcto lo primero sería reiniciar el host ESXi donde se está ejecutando la máquina para que libere el posible bloqueo. Designed and Hosted by Andy Barnes VMdamentals.com VMware Technical Deepdive by Erik Zandboer HomeAbout « Best of VMdamentals.com 2011 posts "My VAAI is Better Than Yours" » Snapshot Consolidation needed - Re: Virtual machine disks consolidation is needed y Unable to Access file
Instead of using the /var/log/messages as mentioned in the KB article I opened vmware.log in vi. 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 To do this just access the CLI and type "services.sh restart" Once that is complete the consolidation should work. Check This Out All Rights Reserved.
Thank you. After the successful datastore relocation the snapshots can be easily consilidated and the VM snapshot has just been fixed. Gracias por todo y felices fiestas. An error occurred while consolidating disks: One or more disks are busy." Resolution: First I shut down the server that had was running the backup job that triggered the issue, but that