Problem with an ESXi server

[fafa24]

Hello,
We have 4 ESXi 6.02 servers which we back up with the Veeam solution. I have found out that when I migrate a VM which we do back up with Veeam this error message returns Veeam in the notification mail

Getting VM info from vSphere
Error: File does not exist or locked. VMFS path: [[DatastoreBlade1] BMZURNT005/BMZURNT005.vmx]. Please, try to download specified file using connection to the ESX server where the VM registered. Failed to create NFC download stream. NFC path: [nfc://conn:BMZURNT021,nfchost:host-2280,stg:datastore-2350@BMZURNT005/BMZURNT005.vmx].

When I migrate the VM to another ESX server the back up goes well without any error. I believe there is an issue with this ESXi server. With migration, I mean only move the VM to another host and not move the datastore. The same happens if I move another VM to this ESXi server.

support ID: 02025387

[Vitaliy S.]

fafa24, does this happen to only 1 host or it happens whenever you migrate to any host? Do you use vCenter Server when doing migration?

[fafa24]

It only happens to one host, the others are fine. I had a quite a few times to find this out.

[Vitaliy S.]

Do you know what's the difference in terms of storage used, management, or anything else between this host and others? This might be the clue to the resolution.

[fafa24]

I have one shared storage which uses all ESXi servers. So in terms of storage I can't see the difference. Also about configuration of the server.

[Vitaliy S.]

Ok, in this case please keep working with our support team, as this issue clearly relates to some configuration option on that very host. Our support team should be able to help you you with nailing down the issue. What if you create a temp VM on that host and migrate it? Can you back it up? Also what happens if you migrate this temp VM back?

[krismason@]

Im having the same issue - any update?

[Mike Resseler]

Kris,

Our engineers are working on it. Please create also a support case for your issue

Thanks
Mike

[Vitaliy S.]

OPs ticket is in German, so I cannot update you with the solution. Please let us know your case ID once you open a ticket.

[fafa24]

Hello,

The resolution for this ticket was a bit simple. I just restarted the ESXi host and now it seems to back up fine

[Vitaliy S.]

Thanks! It seems like restarting ESXi management agents should also do the trick given that the entire restart fixed it.

[fafa24]

In my case I restarted first the management agents from the server console. But this did not help.