This was a good article up to a point, but it could be clearer. Therefore it's important to have scripts, reports and tools like Snapwatcher or opvizor Health Analyzer to get an idea about the current situation in your environment. Then I powered on the Data Protection Appliance but it failed to boot up correctly with the following error: This was the root of the problem, VDP appliance had mounted the problematic Share this:TwitterFacebookGooglePocketLike this:Like Loading... http://webinweb.net/virtual-machine/vmware-unable-to-consolidate-file-is-locked.html
What Went Wrong !!! Nowadays snapshot is been used very widely and regularly when we do any changes but this does create issues when we are not been regular to remove snapshots after we done Subscribe To Our NewsletterJoin our mailing list to receive the latest news and updates from our team. Then the backup was made.
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 am also looking on another scenario where I have same issue on a remote location and datastore is out of space – looking for a solution will update once I It seemed that the backup job did not delete the backup snapshot, let's wipe it out manually. I used the second method (moving the vm to another datastore).
Reply Joy Banerjee on December 21, 2014 at 9:56 am Thanks Raj for dropping off Reply Hausverwaltung Essen on March 13, 2015 at 12:30 pm Its nice one Reply Geo on If it fails it causes only troubles. Many thanks for sharing this! An Error Occurred While Consolidating Disks 5 (input/output Error) The basic option is to follow KB 2003638 and just run a basic consolidation by going to Snapshot -> Consolidate.
Caveat: Not all vmdks removed as part of the consolidation. Notify me of new posts by email. The next error shows that the file is locked. Incapsula incident ID: 108001310283843143-1415315681090209850 Toggle navigation HomeVMwareMicrosoftCitrixLinuxStorageNetworkingOtherAbout Home Resources ESX and ESXi Server Disk Consolidation Needed - Unable to access file since it is locked After deleting snapshots on a VM
You will see a warning message on virtual machine summary Snapshot consolidation needed fails with a lock message Now your task is to clear this message for that you need to An Error Occurred While Consolidating Disks: Could Not Open/create Change Tracking File. There are a number of recommendations around what can be done to remove the lock on the file. Don’t have an account? How to Fix Snapshot consolidation needed fails with a lock message?
Copyright ©2016 Andy Barnes - Please do not copy any content including images without prior consent! When checking the virtual machine log file vmware.log in the home directory of the VM, the following entry can be found: 2015-03-05T20:08:25.112Z| vcpu-0| I120: AIOGNRC: Failed to open '/vmfs/volumes/0025909bfda0/WinVM/WinVM-flat.vmdk' : Failed Virtual Machine Disks Consolidation Failed Share This Story, Choose Your Platform! Virtual Machine Disks Consolidation Is Needed No Snapshots However, when using the command, the corresponding descriptor file for the latest delta disk needs to be used when cloning the disk.
At this point it looked as it the consolidation was going to work but at about 20% it failed. this contact form Notify me of new posts by email. Method - 1 Note the path of the disk files before removing or unlinking them from VM You need to unlink your disk files /vmdk files from virtual machine (Do Not After the successful datastore relocation the snapshots can be easily consilidated and the VM snapshot has just been fixed. Detected An Invalid Snapshot Configuration
Some people recommend reboot the ESXi host to release the lock but per my issue above, there was no vMotion network and these hosts run production manufacturing systems and cannot just Consolidate Virtual Machine Disk Files Stuck 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 SUBSCRIBE!
Job automation is good when it does not fail! Reply KpuCko on October 3, 2015 at 8:20 am Thanks for the post. Incapsula incident ID: 108001310283843143-1415315668205307962 Request unsuccessful. Restart The Management Agents On That Host Related 14 Comments Jay on October 22, 2014 at 10:40 pm This is Great Post - Thanks it helped me Reply Roger on November 24, 2014 at 9:42 pm We have
Whilst the information provided is correct to the best of my knowledge, I am not reponsible for any issues that may arise using this information, and you do so at your This was done by connecting to the ESXi host via SSH and running the following commands: /etc/init.d/hostd restart /etc/init.d/vpxa restart This caused the host to be unmanageable for a brief moment. Required fields are marked *Comment Name * Email * Website Notify me of follow-up comments by email. Check This Out There are few ways which you can opt for to fix this issue – you need to follow the below steps choose your methods.
These issues also get into the picture when we have multiple snapshots for a single Virtual Machine – sometimes it does not get cleared during the snapshot deletion. Sign Up for opvizor Comments are closed. English Localized Websites English Deutsch Français Русский Italiano Español Nederlands 中文(简体) 日本語 Česky Polski Türkçe Português(BR) Español(LA) Resource Pages Svenska עברית Sign In Downloads Contact Sales Sales Hotline: +49-800-100-0058 CET 8:00am Request unsuccessful.
CompetitionCloud and Service ProvidersVCSP Program and Product OfferingsVeeam Availability ConsoleMonitoring and ManagementVeeam ONE9.5Veeam Management Pack for System CenterFree ToolsVeeam Backup Free EditionVeeam Endpoint Backup FREEVeeam Agent for Linux FREEVeeam ONE Free You'll then be prompted to select Yes/No as you'll have to consolidate the Redo logs. This meant the base disks of the VM being backed up where still locked, hence the failure when trying to consolidate. Post navigation ← Cisco UCS - FSM:FAILED: Ethernet traffic flow monitoring configuration error Holidays and Career Reviews → Leave a Reply Cancel reply Your email address will not be published.
Designed and Hosted by Andy Barnes Home Blog Forum Windows Server Active Directory Powershell Sharepoint Forum How to Get IT Job VMware Unix Microsoft Exchange Server Exchange Online Skype For Business Failing to do so results in an outdated destination copy. I ran the following command: # lsof | grep