Error during the configuration of the host: NFS Error: Unable to Mount filesystem: Unable to connect to NFS server
An error occurred during host configuration.
NFS mount <mount_server>:/VeeamBackup_<mount_server> failed: Unable to connect to NFS server.
If the service is running, move to the next troubleshooting step.
If the service is not running, try to start it. If the service fails to start, review KB1094. After the service begins running again, retry the restore operation.
Connect to the Mount Server and determine if another process is locking the port used by the Veeam vPower NFS Service:
Get-Process -Id (Get-NetTCPConnection -LocalPort 111).OwningProcess
If VeeamNFSSvc is listed as locking port 111, move to the next troubleshooting step.
If not, resolve port conflict and retry the restore.
If there are no datastores matching the description provided, move to the next troubleshooting step.
If there were, and you have unmounted them, retry the restore operation.
If you can ping the ESXi host's VMkernel Port IP from the Mount Server, move to the next troubleshooting step.
If the ping fails, resolve the connectivity issue and retry the restore operation.
Connect to the ESXi host specified during the restore operation using SSH and confirm that the host can vmkping the Mount Server associated with the repository where the backup files are located.
The steps above may require that you Enable Acces to the ESXi Shell.
If no connectivity issues were identified, move to the next troubleshooting step.
If there were connection issues, resolve them and then retry the restore operation.
Unable to mount vPower NFS volume (<mountserver_ip>:/VeeamBackup_<mountserver>). Fault "AlreadyExistsFault",
Error The specified key, name, or identifier already exists.
Unable to create datastore VeeamBackup_<mountserver_ip> on host <esxi_host>, because it already exists
Failed to add NFS datastore for NFS host, Failed to mount NFS volume
Starting with Veeam Backup & Replication 9.5 U4, the Veeam vPower NFS Service uses an IP allowlist to control which servers can connect to the NFS share. In some rare cases, Veeam Backup & Replication may not add the IP address of the ESXi host to the IP allowlist.
To isolate whether this is occurring, it is possible to disable the IP authorization control system by creating the following registry value on the Mount Server.
Please note that this value disables built-in IP authentication for vPower datastore and is only recommended for testing purposes.
Key Location: HKLM\SOFTWARE\WOW6432Node\Veeam\Veeam NFS\
Value Name: vPowerNFSDisableIPAuth
Value Type: DWORD (32-Bit) Value
Value Data: 1
After creating the above registry value, restart the Veeam vPower NFS Service.
Retry the restore operation with the above registry value in place on the Mount Server associated with the repository where the backup files are located.
If the restore works with the IP Authorization disabled, contact Veeam Support. We can assist in determining what IP was used to connect to the vPower NFS Share and why it was not automatically added to the allowlist previously.
If the restore still fails, remove the registry value, restart the Veeam vPower NFS Service, and move to the next troubleshooting step.
If the 'VeeamBackup_' datastore could be manually added to the ESXi host, retry the restore operation, making sure to specify the same ESXi to which the datastore was able to be attached.
If the 'VeeamBackup_' datastore could not be manually attached, and you have reviewed all other troubleshooting steps, a much deeper investigation will be necessary. Such analysis may require that you create a case with VMware Support so that a three-way conference call can occur with a VMware Engineer reviewing the logs in the vSphere Environment to help determine why the NFS datastore could not be created.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case