OPERATIONAL DEFECT DATABASE
...
...
BugZero found this defect 4447 days ago.
During a Veeam vPower NFS-based operation (SureBackup, Instant Recovery, Instant Disk Recovery, or Other-OS FLR), the following errors may occur: 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 The Datastore that Veeam Backup & Replication will attempt to create will always start with the prefix 'VeeamBackup_' and the ending with the Mount Server's hostname, FQDN, or IP.
This error occurs when the vSphere Environment cannot create the 'VeeamBackup_' datastore because a datastore already exists with that name, or there is an entry stuck in the Datastore cache. Note: The vPower NFS datastore stays mounted to the ESXi host. Each time you start an operation that would use the datastore, Veeam Backup & Replication checks whether the vPower NFS datastore is mounted to the host. If you manually unmounted the datastore or the datastore was unmounted by other causes, Veeam Backup & Replication remounts the datastore.
Initial Troubleshooting Before proceeding to more advanced troubleshooting steps, determine if a datastore matching the name specified in the error is visible via a vSphere Client. If so, unmount it. Using the vSphere Web Client, connect to the vCenter that manages the ESXi host specified in the error. Review the list of Datastores and unmount the one that matches the datastore name shown in the error. Using the vSphere Web Client, connect directly to the ESXi host specified in the error. Review the list of Datastores that the ESXi host lists, and unmount the one that matches the name shown in the error. Advanced Troubleshooting If the unmount process fails, or there is no datastore matching the name visible, you should consider restarting the management agents on the ESXi host listed in the error. If the issue persists after restarting Management Agents, review KB4167 for details on removing latent entries from the ESXi host's Datastore cache.
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."
