#1 Global Leader in Data Protection & Ransomware Recovery

Unable to Mount VeeamBackup_ Datastore - Specified Key, Name, or Identifier Already Exists

KB ID: 1690
Product: Veeam Backup & Replication | 9.5 | 10 | 11 | 12 | 12.1
Published: 2012-11-13
Last Modified: 2023-10-19
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge


During a Veeam vPower NFS-based operation (SureBackupInstant RecoveryInstant 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.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.