NVP vProxy: Troubleshooting Network Connectivity For Backup and Restore Operations

Systems and ports that are involved for VMware Virtual Machine (VM) backup and restore operations.

Port Requirements

Port requirement table

From	To (target_system)	Port	Purpose
NetWorker Server	vProxy Appliance	9090	NetWorker VMware Protection web service calls to initiate and monitor backups, image recoveries, granular recovers.
NetWorker Server	vCenter Server	443	VMware View in the NetWorker Management Console
NetWorker Server	ESXi Server	443	Emergency Restore, vProxy redeployment
vCenter Server	NetWorker Server	9090	vSphere Client's Dell NetWorker plug-in.
Dell Data Protection Restore Client Interface	NetWorker Server	9090	File-level recovery in the Dell Data Protection Restore Client. Note: This also applies to the NetWorker Web User Interface (NWUI).
ESXi Servers	Data Domain	111, 2049, 2052	File-level recovery and instant recovery.
Virtual Machines	Data Domain	111, 2049	SQL application-consistent backups
vProxy Appliance	Domain Name System (DNS)	53	Name resolution.
vProxy Appliance	Data Domain	22, 111, 131, 161, 2049, 2052, 3009	Data Domain management Note: Port 3009 is required by the vProxy with DDOS 7.0 or later to perform FLR and Instant Access restore.
vProxy Appliance	ESXi Server	443, 902	Backup and recovery operations
vProxy Appliance	vCenter Server	443	vProxy registration, backup, and recover operations.  Note: Using a nondefault vCenter port for HTTPS is not supported.
vProxy Appliance	Target Virtual Machine	9613	vProxy FLR - Communication with the FLR agent on the target VM Note: Port 9613 is used for FLR operations only when available. If the port is not available, then it falls back to the older method through VMware VIX API.

Domain Name System (DNS)

Ensure to check that DNS is resolved correctly for the systems involved; including the Fully Qualified Domain Name (FQDN), Short Name, and IP Address (Reverse Lookup).

nslookup FQDN
nslookup SHORT_NAME
nslookup IP_ADDRESS

See article: Troubleshooting DNS and Name Resolution Issues

It is also advised checking system hosts files. Host file entries may conflict or override a DNS query, or lead to an incorrect IP address or hostname.

• Linux Systems: /etc/hosts
• Windows Systems: C:\Windows\System32\drivers\etc\hosts

NetWorker Server

The NetWorker nsrports command can be used to confirm name resolution and port connectivity between the systems involved. See the above table regarding which ports and target system should be specified when testing communication.

nsrports -t target_system -p port

Linux systems can use the curl command to test connectivity: Windows systems can use Test-NetConnection PowerShell cmdlet:

Test-NetConnection -ComputerName target_system  -port port

vProxy Appliance

The ProxyHC (Health Check) utility can be run on the vProxy to check port connectivity between systems, see article: NVP-vProxy: How to use health check tool ProxyHC on vProxy appliance.

The vProxy appliance can also use the curl command to test connectivity. See the above table regarding which ports and target system should be specified when testing communication.

curl -v target_system:port

ESXi Server

The netcat (nc) command can be used on ESXi hosts to check port connectivity. See the above table regarding which ports and target system should be specified when testing communication.

nc -zv target_system port

See article NVP vProxy: NetWorker VIB to Open NFS Ports For vProxy FLR.

vCenter Server

vCenter servers use operating system-based connection commands. See the above table regarding which ports and target system should be specified when testing communication.

curl -v target_system:port

Virtual Machines

Whether testing communication from a VM for the Data Protection Restore Client, NetWorker Web User Interface (NWUI), or connectivity with Data Domain, the command used depends on the operating system of the virtual machine. Linux systems can use the curl command to test connectivity:

curl -v target_system:port

Windows systems can use Test-NetConnection PowerShell cmdlet:

Test-NetConnection -ComputerName target_system  -port port

Per the NetWorker Security Configuration Guide, NetWorker uses a direct socket connection to communicate and move data across the network to the required service with minimal overhead. While NetWorker opens some ports for TCP and UDP, NetWorker only requires TCP ports. UDP ports are optional, except for SNMP which uses UDP port 161 and 162.

The port table and network topology that is displayed in this KB was pulled directly from the NetWorker VMware Integration Guide. The VMware Integration and Security Configuration Guides can be found on the Dell Support NetWorker Product page.