Operational Defect Database

BugZero found this defect 4177 days ago.

Veeam | kb1690

Unable to Mount VPower NFS Specified Key Name or Identifier Already Exists

Last update date:

10/19/2023

Affected products:

Veeam Backup & Replication

Affected releases:

11

Fixed releases:

No fixed releases provided.

Description:

Challenge

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.

Cause

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.

Solution

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 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.

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:

Additional Resources / Links

Share:

BugZero® Risk Score

What's this?

Coming soon

Status

Solved

cost-cta-background

Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.

Have you ever...

had your data corrupted from a

VMware

bug?

Search:

...