VaultOS 5.0 allows you to specify the port for the VaultOS Client and NVBU server (4046055)

BakBone Tech Tips

There are 2 different TCP connections during Data Transfer between VaultOS and VaultDR Server, Inbound and Outbound from both sides. From 2 different connections and both perspective of VaultOS and VaultDR server, you are looking at 8 different ports number. From VaultOS perspective, there are 2 source and destination ports for the inbound connection and 2 source and destination ports for outbound connection. The same apply for the VaultDR server perspective and the total is 8. From VaultOS side we are listening at port 10,000 on the inbound connection destination port, and not to worry about the inbound connection source port. Once establish the 1st inbound connection from the VaultDR server, VaultOS will initiate a connect back to the VaultDR server on a 2nd outbound connection for data xfer. The 2nd outbound connection destination port is set in the firewall.cfg (NDMP port) on the VaultDR server side. We will not worry about the 2nd connection source port. As for the VaultDR Server side, the initial 1st outbound connection destination port will be 10,000 and this will connect to remote VaultOS. Once the 1st connection established, the VaultDR server will wait and listening for the connect back from VaultOS for data xfer. The listening for 2nd connection destination port will depend on firewall.cfg (NDMP port). If no value is set (DEFAULT), we will bind the listening socket to port 0, which lead to the service provider assignment of a unique port number. This is why some of you see as random.

drdaemon -p <port number>



You can also see page of the Users guide



http://www.bakbone.com/docs/NetVault_Backup_VaultDR_System_Users_Guide.pdf