Unable to Mount VPower NFS Specified Key Name or Identifier Already Exists
Challenge
A vPower NFS operation such as Instant Recovery or SureBackup Virtual Lab creation fails with the following error:
Failed to publish VM "VMNAME"
Unable to mount vPower NFS volume (VPOWERVOLUMENAME). VPOWERHOSTNAME:
The specified key, name, or identifier already exists.
Cause
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.
Solution
/sbin/services.sh 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
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003490
Couldn't find what you were looking for?
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
Do you have an issue or need post-sales technical assistance?
*if you need help choosing the right product, please select "Sales" chat
Do you need guidance on the website, upgrade hints or help with your licenses/accounts?
Questions regarding your Veeam contract renewal? Contact us and learn how you can maximize your savings
Do you need additional license, pricing details, product information or have any other sales-related question?
Would you like to become our partner or do you need assistance as our existing partner?
We apologize, but this chat is not available at the moment
We apologize, but this chat is not available at the moment
We apologize, but this chat is not available at the moment
We apologize, but this chat is not available at the moment
Veeam representative will get back to you shortly.
