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 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 A VMware-level snapshot was made, the base disk was hot-added to the VM that handles the backup. 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 check my blog
That worked perfectly! Copyright © 2016 Opvizor. Reply Raaj says: December 20, 2014 at 11:10 am Great Joy !!! 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
All Rights Reserved. But bugs come typically with weird situations. Once storage migration is complete then you can run the consolation and it will fix the issue. http://www.symantec.com/docs/TECH199999 Beyond that, look out for running too many backups/snapshot operations at the same time.
Removing the base disk from the backup appliance VM was enough to remove the lock, after which consolidation was possible, and problem solved. Note: We could not see the snapshots in the snapshot manager. Post navigation ← How to Migrate Thin Client User Profile from Xen App 5 to Xen App 6.5?How to Fix Events 137 and 57 source NTFS which relates to StorageCraft Shadow An Error Occurred While Consolidating Disks: Could Not Open/create Change Tracking File. This may not solve my issue although it's exactly what is happening.
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 Disk Consolidation Needed - Unable To Access File Since It Is Locked I used the second method (moving the vm to another datastore). I will not go into details which backup product this was though 🙂 So the backup solution of Brand X was trying to backup a VM. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : VMware VM "needs consolidation" after backup failu...
I edit the media server vm and remove the "extra" disks....I can then run disk consolidation on the problem VM. 0 Kudos Reply There is an Alarm definition Stuart_Green Level Consolidate Virtual Machine Disk Files Stuck 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 Then the backup was made. However the consolidate operation may fail again, if the issue which caused the snapshot deletion operation to fail disk consolidation previously has not been cleared. It has been a good
The up side is it's only a lab environment. click site Get a IT Job - Windows Server 2012 Training Videos – Day to Day Task Windows Server 2016 Technical Preview Comparison Guide – Download PDF Recent CommentsThomas on Snapshot consolidation needed Jason says: March 28, 2014 at 22:30 Thank you for the storage vmotion idea. A little history: As I was testing a third party solution of "Brand X", this error occured. An Error Occurred While Consolidating Disks 5 (input/output Error)
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. Subscribe to Blog via Email Enter your email address to subscribe to this blog and receive notifications of new posts by email. Thank you. http://bovbjerg.net/virtual-machine/virtual-pc-cannot-shutdown-a-locked-virtual-machine.php Notify me of new posts by email.
The "fix" for us has been to run "services.sh restart" on the ESXi server - this unlocks the file - then manually consolidating the VM. Detected An Invalid Snapshot Configuration I had went through just about every vmware kb article on consolidation I could find, and nothing was solving this. This time: success!
Like mentioned before the VM is powered off and the file lock message pops up when trying to delete the snapshots. Powered by WordPress and WordPress Theme created with Artisteer. Failing to do so results in an outdated destination copy. The Maximum Consolidate Retries Was Exceeded zSprawl says: May 26, 2014 at 07:02 In my case, a storage vMotion cleared up all issues.
Why Snapshot consolidation needed fails with a lock message? Downloads Contact Sales Call sales: 1-800-691-1991 8am - 8pm ET Back Downloads Contact Sales solutionsProductsHow to buyService ProvidersPartnersResourcesCompanySupport Business sizeEnterprise and Medium BusinessSmall BusinessVertical SegmentFederal Government (FED)State & Local Government/Education (SLED)CloudVeeam I found you through Google and bingo my system is back. http://bovbjerg.net/virtual-machine/virtual-pc-cannot-shut-down-a-locked-virtual-machine.php But the investigation is before the fix, so let´s start with that first.
Yes, when my Veeam was a VM appliance mode system I could go to this server and see disks mounted from the VMs being backed up but not any more. 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 Then the backup was made. 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
And my luck was, that selecting "consolidate" ended in that one brilliant error: Unable to access file since it is locked. This might happen under the hood but it doesn't work the same way when it is a physical server. This meant the base disks of the VM being backed up where still locked, hence the failure when trying to consolidate. Best regards!