Bookmark the permalink. Copyright ©2014 Andy Barnes 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" » Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Veritas.com Support Communities Information Governance Bonnie Bauder says: February 22, 2013 at 02:30 Thank you! click site
Strange enough, also a power on works fine. I really enjoy your blog. When checking the VM and creating new snapshots, all works well. This meant the base disks of the VM being backed up where still locked, hence the failure when trying to consolidate.
Once storage migration is complete then you can run the consolation and it will fix the issue. Request unsuccessful. No snapshot present on the VM which could not be backed up - but a yellow mention in the VI client: "Configuration Issues - Virtual Machine disks consolidation is needed".
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. Required fields are marked *Comment Name * Email * Website Notify me of follow-up comments by email. How to Fix Snapshot consolidation needed fails with a lock message? An Error Occurred While Consolidating Disks: Could Not Open/create Change Tracking File. You saved my day.
Erik Zandboer says: March 8, 2013 at 00:02 Actually in my case there was no ESXi reboot required at all. Disk Consolidation Needed - Unable To Access File Since It Is Locked Resources from VMware Use vmkfstools to clone disk: http://kb.vmware.com/kb/1028042 Hope these above methods will help you to resolve issue of Snapshot consolidation needed fails with a lock message. But the story will end with a VMware bug, that is absolutely weird but luckily easy to fix. 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
After the backup was made however, the backup solution somehow did not manage to hot-remove the disks from the backup VM. Consolidate Virtual Machine Disk Files Stuck Only requires a read-only VM account. 0 Kudos Reply I run into this same thing Bmitche Level 5 06-09-2014 08:13 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed This post saved me a lot of time! Reply Joy Banerjee says: July 6, 2015 at 4:58 pm Sure Thanks Sir - You are Welcome Reply Jorge Bahia says: June 30, 2015 at 11:48 am Thanks it helped me
I wanted to make sure that is how you did it before I proceed. Normally you would expect a locked file message also when starting the VM. Virtual Machine Disks Consolidation Failed What Went Wrong !!! Virtual Machine Disks Consolidation Is Needed No Snapshots Reply Joy Banerjee says: December 21, 2014 at 9:56 am Thanks Raj for dropping off Reply Hausverwaltung Essen says: March 13, 2015 at 12:30 pm Its nice one Reply Geo says:
And my luck was, that selecting "consolidate" ended in that one brilliant error: Unable to access file since it is locked. get redirected here P.S – Do share your views and comments, thanks in advance. LinkedIn Twitter grab this Send to Email Address Your Name Your Email Address Cancel Post was not sent - check your email addresses! We started using VADP backups early on and have found the orphaned snapshot problem is getting a lot less, The lessons we learnt was to: Keep NBU up to date as An Error Occurred While Consolidating Disks 5 (input/output Error)
Actually when the customer approached us with that situation we thought of a Snapwatcher bug during beta. After the migration has done the error disappeared. Reply Raaj says: December 20, 2014 at 11:10 am Great Joy !!! http://ibuildsystem.com/virtual-machine/virtual-pc-cannot-shut-down-a-locked-virtual-machine.php You need right click on VM and click Migrate – you need choose migrate disks to another available datastore - this will clear lock on disk files of the virtual machine.
power down VM 2. Detected An Invalid Snapshot Configuration Running multiple backups of the same VM at the same time. 2. The only 100% solution was to restore from my Veeam backup but I can't do this easily on every server especially DB servers under frequent changes.
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 Backups are hanging. 0 Kudos Reply There are some methods which joyb81 Level 3 Certified 10-09-2014 12:39 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : VMware VM "needs consolidation" after backup failu... The Maximum Consolidate Retries Was Exceeded Ben Greslick says: February 13, 2013 at 19:47 Storage VMotion to another datastore.
Once confirmed I placed the host in maintenance mode, DRS vMotioned all VMs to another host in the cluster and restarted the hostd service. /etc/init.d/hostd restart Once the hostd service had How it was fixed The solution was, as it is most of the time, simple: I manually removed the base disks from the backup VM (without deleting them from disk of Doug Rafuse says: September 17, 2013 at 17:16 Ben's solution of performing a storage vMotion (whether the machine be off or on), then running Consolidate worked perfectly. my review here Incapsula incident ID: 208000420016291003-46213306952712869 Request unsuccessful.
This might not be the solution for me but if anyone can confirm I would appreciate it….I know this post is old and may be abandoned at this point…cheers! Incapsula incident ID: 208000420016291003-91036758179840682 Request unsuccessful. CompetitionCloud and Service ProvidersVCSP Program and Product OfferingsVeeam Availability ConsoleMonitoring and ManagementVeeam ONEv9Veeam Management Pack for System CenterFree ToolsVeeam Backup Free EditionVeeam Endpoint Backup FREEVeeam ONE Free EditionVeeam FastSCP for Microsoft Method – 3 (Good Option to fix – but you need extra space on datastore) For this option you need to power off you virtual machine and then we will clone
VOX : Backup and Recovery : NetBackup : VMware VM "needs consolidation" after backup failu... Sign Up for opvizor Share This Story, Choose Your Platform! Latest Blog Posts View 7 Administrator Blank Error Dialog/Window After Upgrade App-V 5.x Writing to the native registry vSphere Transparent Page Sharing (TPS) in Horizon View 6.1 Mouse Cursor Disappears on Share this:ShareTwitterGoogleEmailFacebook Posted in VMware | Tags: consolidate failed, consolidate fails, consolidate snapshot failed, consolidate snapshot fails, Consolidation, snapshot, Snapshot Consolidation, Unable to access file since it is locked, vmware snapshot
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 Bryan says: July 7, 2014 at 20:53 services.sh restart from cli worked for me as well. As always before performing anything; check, double check, test and always ensure you have a backup. Power on Is this correct-anyone?
Toggle navigation Products Health Analyzer™ Performance Analyzer™ Performance Analyzer – Integrations Snapwatcher™ Plans & Pricing Health Analyzer™ Cloud Performance Analyzer Snapwatcher™ Health Analyzer™ On Premise About Us Team Reseller Technology Partner All Rights Reserved. We normally restart services on the Symantec media appliance and this releases the lock without having to edit or svmotion the vm. You helped A Lot to ME Thanks!!!!
Thanks again. When this warning pops up, the snapshot is already removed from the VM, but the snapshot files could not be consolidated back into the base disk. We successfully have done this when there were a very large number (hundrerds) of snapsots for a box. No snapshots show up in Snapshot Manager on the VMs that have this error.
Login to ESX / ESXi Server from ssh console to run the below command From the ESX/ESXi terminal: vmkfstools -i input output -d format -a adaptertype From the ESX/ESXi terminal: vmkfstools This elanmbx Level 6 06-06-2014 12:38 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content More interesting info. zSprawl says: May 26, 2014 at 07:02 In my case, a storage vMotion cleared up all issues. Running ESXi 5.0u1.