Operational Defect Database
BugZero found this defect 1097 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb4167
NFS share cannot be used
Last update date:
11/12/2021
Affected products:
Veeam Backup & Replication
Affected releases:
ALL
Fixed releases:
No fixed releases provided.
Description:
Challenge
While performing a Guest Files restore for "Linux and other..." the restore operation fails with the following error:
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 Veeam vPower NFS Service Articles: Troubleshooting vPower NFS Datastore Mounting Issues (Main Troubleshooting Article) Veeam vPower NFS Service fails to start How to test manually mounting NFS folder Unable to Mount VPower NFS Specified Key Name or Identifier Already Exists NFS share cannot be used Upgrade of Veeam Backup & Replication fails with Error 1327. Invalid Drive:
