NFS Mount issue post Veeam B&R 9.5 Update 4a installation

[gmcoburn]

Good Morning!

I'm just putting this up to give others a heads up, but has anyone else seen this issue?

We recently applied Update 4a to our Veeam systems, and whilst it went relatively smoothly, we encountered an issue with the custom NFS mount points we had created that were located on a separate drive, away from the default C:\ProgramData\Veeam\Backup\NfsDatastore location.

We used these mount points to share ISOs etc to our VMware infrastrcture, and all prior updates had honoured the custom drectory setting.

After applying the 4A update, the NFS datastores were still shown as available to the ESXi hosts but were empty of any data.

Investigations found that a registry string setting that had been changed from our custom location to the following

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Veeam\Veeam NFS\
String: RootFolder
Value: %ALLUSERSPROFILE%\Veeam\Backup\NfsDatastore

which points to C:\ProgramData\Veeam\Backup\NfsDatastore

Changing this value to our custom location and restarting the Veeam vPower NFS Service resolved the issue, and all NFS datastores on the ESXi hosts then showed the relevant files.

Initially I had thought that it may have been related to the enhanced security of the new NFS registry AllowedAddresses setting, but this was not the case, and leaving that setting to 127.0.0.1 works fine.

This issue affected 3 separate installations of Veeam B&R 9.5, all having the same issue.

Thanks

George

[foggy]

Hi George, are you positive you've upgraded to Update 4a, not just to Update 4? Since similar issue did exist in U4 and should have been addressed in U4a.

EDIT: Checked internally and actually there were two issues, one of which (the one you're seeing) is fixed in one of the next updates, not in the latest U4a.

[gmcoburn]

Hi Foggy,

Update was installed from a freshly downloaded iso, VeeamBackup&Replication_9.5.4.2753.Update4a.iso, so pretty sure 4a was installed.

Thanks

George

[foggy]

Got it. As I mentioned, it will be addressed further down the road.