v9.5 update 1 - NFS issue

[ferrus]

I patched our v9.5 Veeam servers last week, with update 1.
Most thing went smoothly, but there's one outstanding issue I've noticed - that appears to have been caused by the update.

Our VMware vmkernel network is on a different subnet from the ESX servers and Veeam servers, so to create the NFS connections between VMware and Veeam - I had to set up static NFS mappings in vCenter and registry entries on the Veeam servers.

Since the update, the NFS export remains on the main Veeam B&R server - but the three proxy servers have had their registry keys wiped, and the static NFS mappings left 'inactive'.

I'll can recreate them again, but just wondering if anyone else experienced the same issue upgrading?

[ferrus]

specifically the registry key here (but only on the proxy servers):

vmware-vsphere-f24/how-to-use-veeam-vpo ... ml#p177009

Code: Select all

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Veeam\Veeam NFS\Shared Folders\{GUID}

"nfsFolderName"="/VeeamBackup_FQDN OF YOUR BACKUP SERVER" (STRING TYPE)

[ferrus]

Posted this after upgrading to 9.5 Update 1 - but it's either unique to our infrastructure only, or too few people have manual NFS mount points to confirm the issue.

vmware-vsphere-f24/v9-5-update-1-nfs-issue-t41961.html

I've recently installed 9.5 Update 2, and the same issue occured:

The static NFS mount point on the main B&R server is retained
The static NFS mount points on all the proxy/repo servers are wiped, during the upgrade

Location:

Code: Select all

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Veeam\Veeam NFS\Shared Folders\{GUID}

"nfsFolderName"="/VeeamBackup_FQDN OF YOUR BACKUP SERVER" (STRING TYPE)

Could this be confirmed, and resolved for U3/Veeam 10?
Takes a while to set everything back up!

[foggy]

Confirmed, vPowerNFS installation package overwrites registry value. Cannot comment on when it is to be addressed though.

[wooying]

This all start when I tried to upgrade Veeam 9.5 update 3, after the upgrade I cannot get the upgrade to start off any jobs as well as start the service Implements vPower NFS server. When I start Backup & Replication it tell me vPower NFS need to upgrade, but since the service won't start I think that is why it would allow me to upgrade. All jobs are failing can anyone offer me any assistance? I have a case number #03036067 . TIA

[PTide]

Hi,

As far as I can see from your case, the issue has been resolved via means described in this KB article, is that correct?

Thanks