Challenge
While performing a Guest Files restore for "Linux and other..." the restore operation fails with the following error:
Failed to mount restore point.
Linux FLR appliance deploy failed
Failed to connect backup datastore to the ESX(i) host
Failed to add NFS datastore for NFS host, Failed to mount NFS volume
Cause
During a previous Guest Files restore an NFS Datastore named VeeamBackup_<mount.server.name> was mounted to the ESXi host. If that ESXi host then had an unexpected reboot the previously mounted share becomes unavailable after reboot. When the next Guest Files restore begins the Veeam software detects that the NFS Datastore needs to be remounted and attempts to send requests for a new datastore to be created. This operation fails because the ESXi host kept the share name in the cache and does not allow the mounting of a share with the same name.
A reboot does not clear the cache, so restarting ESXi does not fix the issue.
Solution
The following steps are documented by VMware here: https://kb.vmware.com/s/article/1005057
Connect to ESXi by using SSH and run the following commands.
1. Use this command to list all mounted NFS datastores on the host:
More information
Related Articles
KB1055: Troubleshooting vPower NFS Datastore Mounting Issues
KB1094: Veeam vPower NFS Service fails to start
KB1110: Unable to access the virtual machine configuration: Invalid datastore path
KB1284: How to Test Manually Mounting the Veeam vPower NFS Datastore
KB1289: fault.RestrictedVersion.summary
KB1478: SureBackup fails: Failed to call RPC function - Access is Denied
KB1690: Unable to Mount VeeamBackup_ Datastore - Specified Key, Name, or Identifier Already Exists
KB4166: Upgrading/Uninstalling Veeam Backup & Replication fails with "Error 1327. Invalid Drive: [a-z]:\" or "Warning 1327. Invalid Drive [a-z]:\"
KB4167: Linux Guest File Restore Cannot Connect Backup Datastore to ESXi Host
KB4363: Datastore Named 'VeeamBackup_' Listed as Inaccessible
KB4504: SureBackup Job Failure: "The resource 'VeeamBackup_' is in use."
