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.
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:
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.
Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.