Enterprise Workloads Editions: ✅ Business | ✅ Enterprise | ✅ Elite

Firewall rules for data protection of Enterprise Workloads

If a firewall is configured in your environment, ensure that the following patterns are allowed for seamless backups and restores.

*s3.amazonaws.com/*
s3-*.amazonaws.com
s3*.*.amazonaws.com
*.druva.com

Ports and communication protocols

The following table describes the port and communication protocols used for communication between Druva and various VMware components. For more information, see Ports and communication protocols for VMware virtual machines.

📝 Note
Communication happens from a backup proxy to other parties on various ports. Here, the backup proxy is the communication initiator, which is unidirectional. These ports are used for outgoing (unidirectional) communication, not incoming communication. However, data in the form of a response can flow in the opposite direction. Standard system ports such as 22 (SSH) and 2049 (NFS-SERVER) are used for incoming requests.

Port	Communication Protocol	Description
443	HTTPS+SSL	Druva uses Port 443 to establish a secure connection and communication between the following: Backup Proxy to Druva Cloud Backup Proxy to CloudCache Backup Proxy to vCenter Server 📝 Note Port 443 is required if the ESXi host is directly registered with Druva for backup. Backup proxy establishes connection with ESXi host over Port 443 only if it registered with Druva as Standalone ESXi. If the ESXi host is registered with Druva through vCenter Server, backup proxy communicates with the ESXi host over Port 902.
902	TCP/UDP	Druva uses port 902 to establish a connection between the backup proxy and ESXi host registered with Druva through vCenter Server. By default, VMware uses the port 902 for the `vixDiskLib` connection (All Transport Modes). You must use the `VixDiskLib` to access a virtual disk. All operations require a `VixDiskLib` connection to access virtual disk data.
3542	HTTPS+SSL	For application-aware backups, the backup proxy uses VMware Tools to inject two executables and a few supporting files such as certificates into the guest OS of the virtual machine. When the executables run, they start guest OS processes called `guestossvc` and `PhoenixSQLGuestPlugin` . The backup proxy uses the opened port 3542 on the guest OS so that it can communicate with `guestossvc` to run SQL Server backups. Ensure that this port is open on the guest OS. In addition, the backup proxy should reach the virtual machine directly over IPv4. The backup proxy also uses this port to restore databases to the virtual machine.
3545	HTTPS+SSL	For application-aware backups, the SQL executable service `PhoenixSQLGuestPlugin` queries the Microsoft VSS APIs to back up and restore SQL Server databases. The `guestossvc` service interacts with the `PhoenixSQLGuestPlugin` service using this port. The `PhoenixSQLGuestPlugin` service cannot directly communicate with the backup proxy.
3389/22	TCP/UDP	During the backup cycle, the backup proxy sends network packets to Windows virtual machines (where VMware tools are installed) on port 3389 to identify if the RDP port is open or not. For Linux virtual machines, the port is 22, which is used for SSH. This is used for Disaster Recovery or DR restores.
123	UDP	Backup proxy accesses NTP server on Port 123 (UDP) for time synchronization.
443	HTTPS+TLS	Druva uses TLS 2.0 or a secure connection that happens between the following: Backup proxy and Druva Cloud Backup proxy and CloudCache CloudCache and Druva Cloud

Ports and communication protocols for VMware virtual machines

Prerequisites to install VMware backup proxy

Process workflow of application-aware backups on VMware virtual machines

VMware registration FAQs

Getting started with protecting VMware VM