Veeam13 - PortMapper Issues

[Matt.Sharpe]

Hi Guys,

Veeam 13 in my opinion has introduced some annoyances with installation. We have a customer with VeeamONE/VRO installed (which ships with VBR). They also use Server for NFS which utilizes port mapper as part of the configuration.

The only way to achieve the upgrade is to remove Server for NFS > Upgrade to Veeam13 > Disabled/Remove 'vPower for NFS' service > Re-install Server for NFS and reconfigure it. This is going to be the case for every upgrade we do moving forward.

This in my opinion is not ideal. Could it not be looked into to be able to 'skip' the service installation in a future version?

[Dima P.]

Hello Matt,

Just to clarify — is the upgrade conflict caused by a specific port (for example, 443) being occupied? Do you see any error messages in the upgrade engine that we can review?

Thank you!

[Matt.Sharpe]

Hi Dima,

I already know the issue is related to :111 being occupied. In our instance it is by a SYSTEM PID and I'm pretty sure it relates to "Server for NFS" being installed. The annoyance I have, is that the customer doesn't require vPower NFS. It is not a VBR server, it is a VRO (with VeeamONE) server. Yet we're being forced to remove and backup/recreate NFS configurations just to upgrade to V13 and any future one.