and it finally worked. To resolve quite common issue mentioned in KB article above, it would be logical to select the datastore containing the biggest VMDK. Thanks a lot you save me :)ReplyDeleteSimon9 June 2010 at 00:19Thanks Very much - this has saved me a load of time today and possibly a client too...ReplyDeleteTieftonFraktion5 August 2010 at It fixed our locked problem. More about the author
The right answer in that case is to not panic, restart the Veeam server and restart/continue the backup. Cheers, Chris Send PM 2nd February 2010,03:16 PM #11 Chuckster Join Date Jun 2008 Posts 987 Thank Post 158 Thanked 127 Times in 104 Posts Rep Power 46 Yeah, you're Under Configuration tab >> Storage... I'm not showing any other hard drives under the settings of the VM.
Specifically:RemoveSnapshot failed, snapshotRef "snapshot-xxx", timeout "3600000"Unable to access file
Thanks buddy.With Best Wishes,Srinivas Kolla.ReplyDeleteHeston4pres4 September 2010 at 13:28Man thanks for putting this out there, saved me big time!ReplyDeleteukmohan30 September 2010 at 07:17Thank you very much. I searched hours in google and Vmware KB, but nothing ... It sounds like you went to the datastore, right clicked on the VM files and selected copy? I get an error message popping up saying "File
ReplyDeleteStephen Russell15 June 2014 at 16:21I was able to resolve the issue with a storage vMotion. Long post - hope the details help others.. . asked 5 years ago viewed 6711 times active 5 years ago Related 10VMware ESXi - vSphere - Can't exit VM console access2Why is VMware vSphere Client hanging at the console?1Should I My hard drives were connected to an Avamar Proxy for anyone that uses Avamar.
RE: Cannot consolidate virtual machine ArizonaGeek (IS/IT--Management) 23 Jan 14 13:09 I occasionally get this when my Commvault backups fail (for whatever reason) when snapping my VMs. Thanks.ReplyDeleteVillyano7 February 2012 at 00:57Thanks man, you saved my ass...ReplyDeletezadood8 March 2012 at 10:32thanks a million man!ReplyDeleteRPM4 May 2012 at 09:57Major props for this write-up. Close Box Join Tek-Tips Today! I'm not showing any other hard drives under the settings of the VM.
more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed http://ibuildsystem.com/vmware-cannot/vmware-cannot-open-the-disk-the-file-is-too-large.php Guess what? The first error I get is: Code: Message from localhost.localdomain: VMware ESX cannot find the virtual disk "/vmfs/volumes/4b66f14b-2039fd1e-5308-0021- 5a5c344a/MSS-SR-005 - AV/MSS-SR-005 - AV-000001.vmdk". Are you using the ghettoVCB script?
Amit May 29th, 2015Amit(Quote) at 15:03Amit(Quote) | #13 Reply | Quote But can someone tell me why its happening? GRRR. When comparing both datastores, on the original datastore there isn't a file called xxxx-000001.vdmk. click site The location where the snapshots are created is specified by workingDir parameter of VMX file.
Reason: The system cannot find the file specified. Since last week I have now come across a spare server that's been donated on a temporary basis and decided I'd set it up as another host just for testing purposes. The process began to 20% ……… 30%….. 35%.
The last time, the same issue happened with a different VM, but anyway, the problem is the same.I figured out that the job failed, and It couldn't remove the snapshot. (VDR It works the way mentioned here . Also if you only copied those 2 files I think you are missing a few there. Join the community Back I agree Powerful tools you need, all for free.
Very big thanks. However, since I can't manage it with our current vCenter (old!), and simply copying the files won't really work, then I might need to bite the bullet and request a license Thank you so very much ;-)ReplyDeleteJean-Philippe Seguin14 August 2010 at 12:35Thanks, good issue and great paper !ReplyDeleteSrinivas Kolla16 August 2010 at 21:52ED,This is really a nice stuff. navigate to this website Not the answer you're looking for?
Ryan July 15th, 2011Ryan(Quote) at 10:01Ryan(Quote) | #3 Reply | Quote I have no second harddisk in de settings of my VM, but I still receive the message “Unable to access I didn't even think to look there until I found your post. Just in case the new VM is a screw up, it won't impact the other DC.6) bring the VM online and see how it works. Before we could resolve the problem we had 7 generations of snapshots from Veeam on three of our core production servers.
This operation is locking the Virtual machine disks and it is creating Snapshot file. I'm not sure what to try next.... share|improve this answer answered Mar 11 '11 at 20:34 Chadddada 1,3801525 This particular VM host uses the newer 4.1 ESXi hypervisor, while the other hosts in our environment use When I went into the “Snapshot Manager” there were no active snapshots and I couldn’t delete the files.
Stupid question, but presumably if you browse through the datastore then '/vmfs/volumes/4b66f14b-2039fd1e-5308-0021-5a5c344a/MSS-SR-005 - AV/MSS-SR-005 - AV-000001.vmdk' is a valid path and the file does exist on the new server? Viewing the vm folder containing this VM on my San and I can see a lot of delta vmdk files, and a lot of ctk vmdk files. Thanks !ReplyDeleteSpirit17 March 2011 at 01:39Thanks for sharing, saved me a lot of time.ReplyDelete8b791bfa-5edb-11e0-9c02-000bcdcb8a734 April 2011 at 09:50Seriously, thank you. It also has the independent checkbox checked.Select one by one the extra hard disks and click "Remove".
Chris Send PM SHARE: + Post New Thread Similar Threads VMWare ESXi 4 failed to backup x64 Windows VM - Cannot create a quiesced snapshot By albertwt in forum Thin