Error: NFC storage connection is unavailable.
Failed to create NFC download stream.
Failed to create NFC upload stream.
The cause of most NFC errors fall into 4 primary categories:
*If the account that Veeam Backup & Replication is using to communicate with the VMware Environment has granular permissions set, please confirm all permissions are set according to the Granular Permissions Guide.
Due to the nature of NFC as a client<->server type connection, there is also potential that all things may be correct on the Veeam client-side, and there exists an issue within the VMware Infrastructure itself.
To investigate the potential of DNS, Ports, Permissions, or File Lock issues, you will need to review the Agent process logs.
Creating NFC download stream
nfc| Resolving host name (esx1) to IP address... nfc| Resolving host name (esx1) to IP address... Failed.
nfc| Establishing connection with the host [esx1]. Port: . Failed.
nfc| Sending authd message: [SESSION ID NUMBER]. nfc| Sending authd message: [Name of Host]. nfc| Waiting for the authd reply message...
nfc | Starting file download. File: [[datastore] Test/Test.vmx]. Failed. ERR |Failed to start file downloading from host [esx1]. File path: [[datastore] Test/Test.vmx]. ERR |DiskLib error: .The file is locked or in use – File open failed: File not open --tr:Failed to start file downloading. VMFS path: [[datastore] Test/Test.vmx].
The proxy must be able to resolve the hostname or FQDN of the ESXi hosts in the Virtual Infrastructure.
Further testing can be done using the following PowerShell command. The destination should be the hostname/FQDN/IP shown in the logs for the host.
Test-NetConnection -ComputerName "<destination_host>" -Port 902
When a vCenter Server or standalone ESXi host is added to the [Backup Infrastructure] section of Veeam Backup & Replication, the user assigns an account to be used. That account should have sufficient privileges to all objects related to the VM being backed up.
If the account that Veeam Backup & Replication is using to communicate with the VMware Environment has granular permissions set please confirm all permissions are set according to the Granular Permissions Guide.
In certain circumstances, the ESXi host may establish a lock on VM files, preventing Veeam from accessing the file.
For more information, review the following VMware KB article regarding file locks:
Investigating virtual machine file locks on ESXi hosts (10051)
In some cases, Restarting the Management Agents on the ESXi host may correct NFC connection issues.
The proxy being used to process a VM can be identified by opening the “Task” log specific to the VM from inside the folder named after the job in %programdata%\Veeam\Backup. Searching the Task log for the words “starting agent” will allow for the identification of which server performed the task.
Further information can be found in this forum post: http://forums.veeam.com/veeam-backup-replication-f2/failed-to-create-nfc-download-stream-t2991-15.html#p69806
The NFC connection requires the following:
An issue with Port 902 may represent an issue with a firewall on the ESXi host, Veeam Proxy, or the connection between the two.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case