File does not exist or locked...

[EBoucq]

Hi,

I have backups failing with that error "File does not exist or locked. VMFS path: .......vmx"
I'm wondering if that error could come from the fact we have 2 Veeam servers (dual room configuration) connected to the same vCenter.

Thanks.
Eric

[Vitaliy S.]

Hi Eric,

Please include a support case ID to your post, otherwise this post will be removed by a moderator for not following forum rules. As to the issue, then if this VM is not backed up at the same by two Veeam servers, then it should not be a problem.

Thanks!

[emachabert]

I saw that error for the first time this week at a customer location. On a setup that was working for a year without any issue.
After looking at the job logs, i saw that one of the ESX had problems when opening the NFC channel (authd daemon not responding).
After restarting management agent on the host, the problem went away, but appeared again the next day.
The customer has put the host into maintenance mode and it will be patched soon as it isn't running the same 5.5 build (newer that the rest of the cluster by the way).

[Vitaliy S.]

Yes, if this issue is not caused by another backup job running, then restarting management agents on the host usually releases all the locks on the files.

[EBoucq]

Thank you guys ! I'll try that and let you know !!

[VIP]

Eric,

If you are using HP hardware it could also be the HP-AMS plugin, we had the same error, followed by some other issue's.

http://kb.vmware.com/selfservice/micros ... Id=2085618

Peter

[EBoucq]

Thanks Peter !

[EBoucq]

I tried to restart the management agents. I got tons of lines with the message "can't fork"....It finally stopped but I didn't know if the agents were restarted correctly. The backup kept failing so I decided to reboot the ESXi and now it works !

Thanks everybody.

[bschmidt25]

We had an HA event on one of our hosts the other day and ever since then have been experiencing the following error on specific VMs ("Error: File does not exist or locked"). I have already restarted the management agents and the host these machines are running on, but the error seems to be following the VMs to whatever host I place them on. What other steps should I take to resolve this? Veeam server version is v8 update 3. Hosts are 5.5U3. Thanks in advance.

[Shestakov]

Hello Bryan,
That was a known issue for early v8 releases, fixed in v8u3. Since you are already on the latest v8 version, I would suggest to contact technical support team.
Thanks!

[bschmidt25]

Will do. Thank you!

[Shestakov]

Once you get the support case number please post it here for us to follow the investigation.
Thanks!