1-800-691-1991 | 9am - 8pm ET

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


A vPower NFS operation such as Instant Recovery or SureBackup Virtual Lab creation fails with the following error:

Failed to publish VM "VMNAME"
The specified key, name, or identifier already exists.


One of the most common reasons this issue will occur is that there is an NFS datastore with the same name already mounted and for whatever reason, it was not removed previously or the VC/Host has references to it still in its records.

The below solution is applicable if the NFS datastore does not show up when connected to the VC using the vSphere client.  However, when logged into the host directly you see an NFS datastore. This datastore is most likely marked as inactive and greyed out.


While logged into the host you are attempting to mount the NFS datastore to directly, using the vSphere client, remove the NFS datastore.  If this does not work, then you may need to restart the management agents which can be accomplished with the following command run from an SSH to the host:

/sbin/ restart

It is advised to review the VMware KB article below if you are not familiar with doing this to ensure that all VMs on the host stay powered on and operational during this process.

More information

VMware KB article on restarting management agents on a host:
KB ID: 1690
Product: Veeam Backup & Replication
Version: 5.x, 6.x, 7.x
Published: 2012-11-13
Last Modified: 2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.


error icon

Oops! Something went wrong.

Please go back try again later.