vPower NFS operations fails after upgrade to v6.5

[smile_dav]

Hi,

Just ran into a little issue after upgrading to 6.5 from 6.1.
I performed an Instant Recovery and SureBackup, they both had the following error:

Failed to publish VM "VMNAME"
Unable to mount vPower NFS volume (VPOWERVOLUMENAME). VPOWERHOSTNAME:
The specified key, name, or identifier already exists.
etc etc

Basically, the NFS was still mounted on the ESX(i) host when the upgrade took place (even though I'm pretty sure it wasn't visible in vSphere Client), and all you have to do is ssh to the ESX(i) host, then type the following command to restart the management agent:

/sbin/services.sh restart

You should be able to run your SureBackup and Instant Recovery jobs now.

[Gostev]

Hi, thanks for sharing!

[peposimo]

I had almost the same problem with upgrading from version 5 to 6.5. I can share with Veeam team how I solved it through e-mail, because I have lot of screenshots there.

[Hawen]

Hi

Would file a support case if I had the customer login details. Trying to get them...

I upgraded Veeam to version 6.5 patch 3 and VMware vCenter to 5.1 at a customer site yesterday and now everything related to NFS-exports seems broken.

The NFS-mount on ESX is gone. I cannot use the virtual lab.

When recreating the virtual lab it tries to mount VeeamBackup_<servername> to the ESX host and fails. What directory should be NFS-shared as "VeeamBackup_<servername>" on the Veeam server (NFS-root?). I think i might have to re-export that directory manually with proper share name/permissions.

I have verified that I can NFS-mount a directory on the Veeam server to ESX.

Regards Hans

[Hawen]

Trying to perform Instant recovery:

NFS mount 10.XX.XX.XX:/VeeamBackup_servername failed: The mount request was denied by the NFS server. Check that the export exists and that the client is permitted to mount it.

[foggy]

Hans, could you please try the solution given above and let us know the results? Also, here is the procedure on how to mount the vPower NFS datastore manually.

Hope this helps.

[Hawen]

Thanks I´ll try that although the ESX-hosts have been rebooted (maintenance mode/patching) after Veeam upgrade.

As previously mentioned Im getting the follow error message: NFS mount 10.XX.XX.XX:/VeeamBackup_servername failed: The mount request was denied by the NFS server. Check that the export exists and that the client is permitted to mount it.

"Check that the export exists...". What directory is supposed to be exported? The NFS-root?

Regards Hans

[foggy]

Yes, this is the vPower NFS root folder specified during Veeam B&R setup.

[tsightler]

You might be best to open a support case as I've seen this issue before and there can be quite a few causes. Once thing I would suggest is to stop the vPower NFS server, verify that the process actually stops (look in Task Manager for VeeamNFSSvc.exe and kill it if it's still running). Then uninstall the vPower NFS service via the control panel. Once this is done, select the repository, choose "Properties" and run back through the wizard, when it gets to the "vPower NFS" tab it should detect that the vPower NFS service is missing and reinstall it. After those steps try it again and see if it works.

[Hawen]

Thanks. Got NFS to work but are now having new problems...

SureBackup jobs fails at step Powering on VM: Unable to communicate with remote host, since it´s disconnected.

Instant recovery fails while registering VM: Failed to publish VM "VM_name". Failed: UpdateNetworkAdapter2vm, cannot find virtual ethernet card with nic [4000]

ESX-hosts where patched to 5.0, build 1024429. VM network adapters are vmxnet3.

[foggy]

Glad you've nailed the NFS datastore issue. Regarding the second error, I strongly recommend contacting technical support as logs investigation is required. Btw, here is the adjacent topic discussing similar issues.

[Hawen]

Thanks. I suppose I better open a support case.

[veremin]

I suppose I better open a support case.

Thanks. Kindly please update the topic with the support case ID (and actual solution, once found) for future reference.