Hi, can you provide some extra context. Is this for a particular VM, or server, or every backup job? What version of vsphere are you using? What version of Veeam are you using?

As per Michael we need more details to try to help out. Also check the logs here C:\ProgramData\Veeam\Backup

@compute - As noted, we do need more info to assist. Can you share a screenshot of the error and what step you’re getting it on? I assume from a Backup job, but don’t wanna be too presumptuous.

Hi @compute -

I’m just following up on your NFC Storage error post. Do you still have a problem? If not, can you share what you did to resolve your issue? Or if still not resolved, can you provide further info so we can try to assist?

Thank you.

​@nikolapintaric -

I recommend you get in touch with Veeam Support.

its typically if you have an issue with dns of vcenter or esx hosts

for example if one esx lost dns record like proxy server is not able to resolve ip of esx or certificate of vcenter could be as well

I vote DNS or firewall rules.  Open a ticket, check your logs, and check your firewall, try and ping everything from within the Veeam proxies and repos. 

I had this pop up recently when someone reloaded an ESXi host, but changed the subnet.  

I had such an issue in April, when someone enabled on esx host local firewall and port 902/tcp was blocked from VBR/proxy server.

I also faced similar issue when port 902 was blocked from the VBR to the ESXi host. Please check the communication from VBR to ESXi hosts