This is an archive version of the document. To get the most up-to-date information, see the current version.

Used Ports

On backup infrastructure components, Veeam Backup & Replication automatically creates firewall rules for the required ports. These rules allow communication between the components.

Used Ports Important!

Some Linux distributions require firewall and/or security rules to be created manually. For details, see this Veeam KB article.

You can find the full list of the ports below.

Backup Server Connections
Veeam Backup & Replication Console Connections
Microsoft Windows Server Connections
Linux Server Connections
Backup Proxy Connections
Backup Repository Connections
NFS Repository Connections
Object Storage Repository Connections
Dell EMC Data Domain System Connections
HPE StoreOnce Connections
Gateway Server Connections
Mount Server Connections
Proxy Appliance (Multi-OS FLR) Connections
WAN Accelerator Connections
Tape Server Connections
NDMP Server Connections

VM Guest OS Connections
Veeam U-AIR Connections
Microsoft Azure Proxy Connections
Microsoft Azure Stack Connections
Proxy Appliance Connections (Restore to Amazon EC2)
Microsoft Active Directory Domain Controller Connections During Application Item Restore
Microsoft Exchange Server Connections During Application Item Restore
Microsoft SQL Server Connections During Application Item Restore
SMTP Server Connections
Veeam Backup Enterprise Manager Connections
Veeam Explorers Connections
Veeam Cloud Connect Connections
Veeam Agent for Microsoft Windows Connections
Veeam Agent for Linux Connections
Veeam Plug-ins for Enterprise Applications Connections
Internet Connections

Backup Server Connections

The following table describes network ports that must be opened to ensure proper communication of the backup server with backup infrastructure components.

From	To	Protocol	Port	Notes
Virtualization Servers
Backup server	SCVMM	WCF	8100	Default VMM Administrator Console to VMM server port required by the Veeam Backup Management.
	SCVMM	TCP	8732	Port used as the control channel to the SCVMM server. This port must be opened on the backup server only.
	Microsoft Hyper-V server	TCP	445 1351	Ports required for deploying Veeam Backup & Replication components.
		TCP	6160	Default port used by the Veeam Installer Service.
		TCP	6162	Default port used by the Veeam Data Mover Service.
		TCP	6163	Default port used to communicate with Veeam Hyper-V Integration Service.
		TCP	2500 to 33002	Default range of ports used as transmission channels for jobs. For every TCP connection that a job uses, one port from this range is assigned.
		TCP	49152 to 65535 (for Microsoft Windows 2008 and newer)	Dynamic port range. For more information, see this Microsoft KB article.
Other Servers
Backup server	Microsoft SQL Server hosting the Veeam Backup & Replication configuration database	TCP	1433	Port used for communication with Microsoft SQL Server on which the Veeam Backup & Replication configuration database is deployed (if you use a Microsoft SQL Server default instance). Additional ports may need to be open depending on your configuration. For more information, see Microsoft Docs.
	DNS server with forward/reverse name resolution of all backup servers	UDP	53	Port used for communication with the DNS Server.
	Veeam Update Notification Server (dev.veeam.com)	TCP	80	Default port used to download information about available updates from the Veeam Update Notification Server over the Internet.
	Veeam License Update Server (vbr.butler.veeam.com, autolk.veeam.com)	TCP	443	Default port used for license auto-update.
Backup Server
Backup server	Backup server	TCP	9501	Port used locally on the backup server for communication between Veeam Broker Service and Veeam services and components.
Remote Access
Management client PC (remote access)	Backup server	TCP	3389	Default port used by the Remote Desktop Services. If you use third-party solutions to connect to the backup server, other ports may need to be open.

1 Port 135 is optional to provide faster deployment.

2 This range of ports applies to newly added backup infrastructure components. If you upgrade to Veeam Backup & Replication 10.0 from earlier versions of the product, the range of ports from 2500 to 5000 applies to the already added components.

Veeam Backup & Replication Console Connections

The following table describes network ports that must be opened to ensure proper communication with the Veeam Backup & Replication console installed remotely.

From	To	Protocol	Port	Notes
Veeam Backup & Replication Console	Backup server	TCP	9392	Port used by the Veeam Backup & Replication console to connect to the backup server.
		TCP	10003	Port used by the Veeam Backup & Replication console to connect to the backup server only when managing the Veeam Cloud Connect infrastructure.
		TCP	9396	Port used by the Veeam.Backup.UIService process for managing database connections.
Veeam Backup & Replication Console	Mount server (if the mount server is not located on the console)	TCP	2500 to 33001	Default range of ports used as data transmission channels. For every TCP connection that a job uses, one port from this range is assigned.

1 This range of ports applies to newly added backup infrastructure components. If you upgrade to Veeam Backup & Replication 10.0 from earlier versions of the product, the range of ports from 2500 to 5000 applies to the already added components.

Microsoft Windows Server Connections

The following table describes network ports that must be opened to ensure proper communication with Microsoft Windows servers.

Each Microsoft Windows server that is a backup infrastructure component or a machine for which you enable application-aware processing must have these ports opened. If you want to use the server as a backup infrastructure component, you must also open ports that the component role requires.

For example, if you assign the role of a backup proxy to your Microsoft Windows server, you must open ports listed below and also ports listed in the Backup Proxy Connections section.

The Microsoft Windows server that acts as an SMB file share requires only network ports listed below. The Microsoft Windows server that acts as an NFS file share requires network ports listed below and also ports listed in the NFS Repository Connections.

From	To	Protocol	Port	Notes
Backup server	Microsoft Windows server	TCP	445	Port required for deploying Veeam Backup & Replication components.
Hyper-V server/Off-host backup proxy		TCP	6160	Default port used by the Veeam Installer Service.
Backup repository		TCP	2500 to 33001	Default range of ports used as data transmission channels and for collecting log files. For every TCP connection that a job uses, one port from this range is assigned.
Gateway server		TCP	6162	Default port used by the Veeam Data Mover Service.
Mount server		TCP	49152 to 65535 (for Microsoft Windows 2008 and newer)	Dynamic port range. For more information, see this Microsoft KB article.
WAN accelerator
Tape server
Backup server	SMB3 server	TCP	6160	Default port used by the Veeam Installer Service.
Backup server	SMB3 server	TCP	6162	Default port used by the Veeam Data Mover Service.

Linux Server Connections

The following table describes network ports that must be opened to ensure proper communication with Linux servers.

Each Linux server that is a backup infrastructure component or a machine for which you enable application-aware processing must have these ports opened. If you want to use the server as a backup infrastructure component, you must also open ports that the component role requires.

For example, if you assign the role of a backup repository to your Linux server, you must open ports listed below and also ports listed in the Backup Repository Connections section.

The Linux server that acts as an SMB file share requires only network ports listed below. The Linux server that acts as an NFS file share requires network ports listed below and also ports listed in the NFS Repository Connections.

From	To	Protocol	Port	Notes
Backup server	Linux server	TCP	22	Port used as a control channel from the console to the target Linux host.
Backup server	Linux server	TCP	2500 to 33001	Default range of ports used as data transmission channels. For every TCP connection that a job uses, one port from this range is assigned.
Linux server	Backup server	TCP	2500 to 33001	Default range of ports used as data transmission channels. For every TCP connection that a job uses, one port from this range is assigned.

Backup Proxy Connections

The following table describes network ports that must be opened to ensure proper communication of backup proxies with other backup components. File proxies in NAS backup use the same network ports as backup proxies.

From	To	Protocol	Port	Notes
Backup server	Off-host backup proxy	Off-host backup proxy is a Microsoft Windows server, and it requires the ports listed in Microsoft Windows Server Connections to be opened.
Communication with Backup Server
Backup server	Off-host backup proxy	TCP	6163	Default port used by the Hyper-V Integration Service.
	SMB3 server	TCP	6163	Default port used by the Hyper-V Integration Service.
	Off-host file proxy	TCP	6210	Default port used by the Veeam Backup VSS Integration Service for taking a VSS snapshot during the SMB file share backup.
Communication with Backup Repositories
Hyper-V server/ Off-host backup proxy	Microsoft Windows server	TCP	49152 to 65535 (for Microsoft Windows 2008 and newer)	Dynamic port range. For more information, see this Microsoft KB article.
	SMB (CIFS) share	TCP	445 1351	Ports used as a transmission channel from the backup proxy to the target SMB (CIFS) share.
	NFS share	TCP, UDP	111, 2049	Ports used as a transmission channel from the backup proxy to the target NFS share.
	Gateway server	TCP UDP	49152 to 65535 (for Microsoft Windows 2008 and newer)	Dynamic port range. For more information, see this Microsoft KB article.
Communication with Backup Proxies
Hyper-V server	Backup proxy (onhost or offhost)	TCP	2500 to 33002	Default range of ports used as transmission channels for replication jobs. For every TCP connection that a job uses, one port from this range is assigned.
Microsoft SMB3 server	Backup proxy (onhost or offhost)	TCP	2500 to 33002	Ports used to retrieve CBT information from a Microsoft SMB3 server managing shares that host VM disks.

1 Port 135 is optional to provide faster deployment.

Backup Repository Connections

The following table describes network ports that must be opened to ensure proper communication with backup repositories. Cache repositories in NAS backup use the same network ports as backup repositories.

From	To	Protocol	Port	Notes
Hyper-V server/ Off-host backup proxy	Microsoft Windows server performing the role of the backup repository	Ports listed in Microsoft Windows Server Connections must be opened.
Hyper-V server/ Off-host backup proxy	Linux server performing the role of the backup repository	Ports listed in Linux Server Connections must be opened.
Backup repository	Backup proxy	TCP	2500 to 33001	Default range of ports used as transmission channels for replication jobs. For every TCP connection that a job uses, one port from this range is assigned.
Source backup repository	Target backup repository	TCP	2500 to 33001	Default range of ports used as transmission channels for backup copy jobs. For every TCP connection that a job uses, one port from this range is assigned. Ports 2500 to 3300 are used for backup copy jobs that do not utilize WAN accelerators. If the backup copy job utilizes WAN accelerators, make sure that ports specific for WAN accelerators are open.
Microsoft Windows server running vPower NFS Service	Backup repository gateway server working with backup repository	TCP	2500 to 33001	Default range of ports used as transmission channels during Instant VM Recovery, SureBackup or Linux file-level recovery. For every TCP connection that a job uses, one port from this range is assigned.

1 This range of ports applies to newly added backup infrastructure components. If you upgrade to Veeam Backup & Replication 10 from earlier versions of the product, the range of ports from 2500 to 5000 applies to the already added components.

NFS Repository Connections

The following table describes network ports that must be opened to ensure proper communication with NFS shares added as backup repositories.

From	To	Protocol	Port	Notes
NFS backup repository	Gateway server (Microsoft Windows/Linux)	TCP UDP	2049	Default NFS port.
NFS backup repository	Gateway server (Microsoft Windows/Linux)	TCP UDP	111	Port used for rpcbind service.
NFS backup repository (for repositories supporting NFS protocol version 3)	Gateway server (Microsoft Windows/Linux)	TCP UDP	mountd_port	Dynamic port used for mountd service. Can be assigned statically.
		TCP UDP	statd_port	Dynamic port used for statd service. Can be assigned statically.
		TCP	lockd_port	Dynamic TCP port used for lockd service. Can be assigned statically.
		UDP	lockd_port	Dynamic UDP port used for lockd service. Can be assigned statically.
Microsoft Windows server performing the role of the gateway server	NFS repository	Ports listed in Microsoft Windows Server Connections must be opened.
Linux server performing the role of the gateway server	NFS repository	Ports listed in Linux Server Connections must be opened.
Gateway server (specified in the NFS repository settings)	NFS repository	TCP UDP	111, 2049	Standard NFS ports used as a transmission channel from the gateway server to the target NFS share.

Object Storage Repository Connections

The following table describes network ports and endpoints that must be opened to ensure proper communication with object storage repositories.

From	To	Protocol	Port/Endpoint	Notes
Gateway server	Amazon S3 Object Storage	TCP	443	Used to communicate with Amazon S3 Object Storage. Consider that certificate verification endpoints (CRL URLs and OCSP servers) are subject to change. The actual list of addresses can be found in the certificate itself.
		HTTPS	Cloud endpoints: .amazonaws.com (for both Global and Government regions) .amazonaws.com.cn (for China region) A complete list of connection endpoints can be found in this Amazon article.
		TCP	80	Used to verify the certificate status. Consider that certificate verification endpoints (CRL URLs and OCSP servers) are subject to change. The actual list of addresses can be found in the certificate itself.
		HTTP	Certificate verification endpoints: *.amazontrust.com
	Microsoft Azure Object Storage	TCP	443	Used to communicate with Microsoft Azure Object Storage. Consider the following: The <xxx> part of the address must be replaced with your actual storage account URL, which can be found in the Azure management portal. Certificate verification endpoints (CRL URLs and OCSP servers) are subject to change. The actual list of addresses can be found in the certificate itself. The *.d-trust.net endpoint is used for the Germany region only.
		HTTPS	Cloud endpoints: xxx.blob.core.windows.net (for Global region) xxx.blob.core.chinacloudapi.cn (for China region) xxx.blob.core.cloudapi.de (for Germany region) xxx.blob.core.usgovcloudapi.net (for Government region)
		TCP	80
		HTTP	Certificate verification endpoints: ocsp.digicert.com ocsp.msocsp.com *.d-trust.net	Used to verify the certificate status. Consider the following: Certificate verification endpoints (CRL URLs and OCSP servers) are subject to change. The actual list of addresses can be found in the certificate itself. The *.d-trust.net endpoint is used for the Germany region only.
	IBM Cloud Object Storage	TCP/HTTPS	Customizable and depends on device configuration	Used to communicate with IBM Cloud Object Storage.
	S3 Compatible Object Storage	TCP/HTTPS	Customizable and depends on device configuration	Used to communicate with S3 Compatible Object Storage.

For more information, see Object Storage Repository.

Dell EMC Data Domain System Connections

From	To	Protocol	Port	Notes
Backup server or Gateway server	Dell EMC Data Domain	TCP	111	Port used to assign a random port for the mountd service used by NFS and DDBOOST. Mountd service port can be statically assigned.
		TCP	2049	Main port used by NFS. Can be modified using the ‘nfs set server-port’ command. Command requires SE mode.
		TCP	2052	Main port used by NFS MOUNTD. Can be modified using the 'nfs set mountd-port' command in SE mode.
Backup server	Gateway server	Ports listed in Gateway Server Connections must be opened.

For more information, see Dell EMC Documents.

HPE StoreOnce Connections

From	To	Protocol	Port	Notes
Backup server or Gateway server	HPE StoreOnce	TCP	9387	Default command port used for communication with HPE StoreOnce.
Backup server or Gateway server	HPE StoreOnce	TCP	9388	Default data port used for communication with HPE StoreOnce.
Backup server	Gateway server	Ports listed in Gateway Server Connections must be opened.

Gateway Server Connections

The following table describes network ports that must be opened to ensure proper communication with gateway servers.

From	To	Protocol	Port	Notes
Backup server	Microsoft Windows server performing the role of the gateway server	Ports listed in Microsoft Windows Server Connections must be opened.
Backup server	Linux server performing the role of the gateway server (if a gateway server is specified explicitly in NFS backup repository settings)	Ports listed in Linux Server Connections must be opened.
Gateway server (if a gateway server is specified explicitly in SMB (CIFS) backup repository settings)	SMB (CIFS) share	TCP	445 1351	Ports used as a transmission channel from the gateway server to the target SMB (CIFS) share.
Gateway server (if a gateway server is specified explicitly in NFS backup repository settings)	NFS share	TCP, UDP	111, 2049	Ports used as a transmission channel from the gateway server to the target NFS share.

1 Port 135 is optional to provide faster deployment.

Mount Server Connections

The following table describes network ports that must be opened to ensure proper communication with mount servers.

From	To	Protocol	Port	Notes
Backup server	Mount server	Mount server is a Microsoft Windows server, and it requires the ports listed in Microsoft Windows Server Connections to be opened.
Backup server	Mount server	TCP	6170	Port used for communication with a local or remote Mount Service.
Mount server (or machine running the Veeam Backup & Replication console)	Backup server	TCP	9401	Port used for communication with the Veeam Backup Service.
Mount server (or machine running the Veeam Backup & Replication console)	Backup repository	TCP	2500 to 33001	Default range of ports used for communication with a backup repository.
Mount server	Helper appliance	TCP	22	Default SSH port used as a control channel.
Mount server	Helper appliance	TCP	2500 to 2600	Default range of ports used for communicating with the appliance.
Mount server	VM guest OS	Ports listed in VM Guest OS Connections must be opened.

Proxy Appliance (Multi-OS FLR) Connections

From	To	Protocol	Port	Notes
Backup server	Helper appliance	TCP	22	Port used as a communication channel from the backup server to the proxy appliance in the multi-OS file-level recovery process.
	Helper appliance	TCP	2500 to 33001	Default range of ports used as data transmission channels. For every TCP connection that a job uses, one port from this range is assigned.
	VM guest OS	TCP	2500 to 33001	Default range of ports used as data transmission channels. For every TCP connection that a job uses, one port from this range is assigned.
Helper appliance	VM guest OS	TCP	22	Port used as a communication channel from the proxy appliance to the Linux guest OS during multi-OS file-level recovery process.
		TCP	20	[If FTP option is used] Default port used for data transfer.
		TCP	2500 to 33001	Default range of ports used as data transmission channels. For every TCP connection that a job uses, one port from this range is assigned.
VM guest OS	Helper appliance	TCP	22	Port used as a communication channel from the proxy appliance to Linux guest OS during multi-OS file-level recovery process.
VM guest OS	Helper appliance	TCP	21	[If FTP option is used] Default port used for protocol control messages.
Helper appliance	Backup repository	TCP	2500 to 33001	Default range of ports used as data transmission channels. For every TCP connection that a job uses, one port from this range is assigned.

WAN Accelerator Connections

The following table describes network ports that must be opened to ensure proper communication between WAN accelerators used in backup copy jobs and replication jobs.

From	To	Protocol	Port	Notes
Backup server	WAN accelerator (source and target)	WAN accelerator is a Microsoft Windows server, and it requires the ports listed in Microsoft Windows Server Connections to be opened.
		TCP	6160	Default port used by the Veeam Installer Service.
		TCP	6162	Default port used by the Veeam Data Mover Service.
		TCP	6164	Controlling port for RPC calls.
WAN accelerator (source and target)	Backup repository (source and target)	TCP	2500 to 33001	Default range of ports used by the Veeam Data Mover Service for transferring files of a small size such as GuestIndexData.zip and others. A port from the range is selected dynamically.
WAN accelerator	WAN accelerator	TCP	6164	Controlling port for RPC calls.
WAN accelerator	WAN accelerator	TCP	6165	Default port used for data transfer between WAN accelerators. Ensure this port is open in firewall between sites where WAN accelerators are deployed.

Tape Server Connections

The following table describes network ports that must be opened to ensure proper communication with tape servers.

From	To	Protocol	Port	Notes
Backup server	Tape server	Tape server is a Microsoft Windows server, and it requires the ports listed in Microsoft Windows Server Connections to be opened.
		TCP	6166	Controlling port for RPC calls.
		TCP	2500 to 33001	Default range of ports used as data transmission channels. For every TCP connection that a job uses, one port from this range is assigned.
Tape server	Backup repository, gateway server or proxy server	Tape server is a Microsoft Windows server, and it requires the ports listed in Microsoft Windows Server Connections to be opened.

NDMP Server Connections

The following table describes network ports that must be opened to ensure proper communication with NDMP servers.

From	To	Protocol	Port	Notes
Gateway server	NDMP server	NDMP	10000	Port used for data transfer between the components.

VM Guest OS Connections

The following table describes network ports that must be opened to ensure proper communication of the backup server with the runtime coordination process deployed inside the VM guest OS for application-aware processing and indexing.

From	To	Protocol	Port	Notes
Backup server	Linux VM guest OS	TCP	22	Default SSH port used as a control channel.
	Guest interaction proxy	TCP	6190	Port used for communication with the guest interaction proxy.
		TCP	6290	Port used as a control channel for communication with the guest interaction proxy.
		TCP	445	Port used as a transmission channel.
Guest interaction proxy or Mount server	Microsoft Windows VM guest OS	TCP	445 1351	Ports required to deploy the runtime coordination process on the VM guest OS.
		TCP	49152 to 65535 (for Microsoft Windows 2008 and newer)	Dynamic port range used by the runtime process deployed inside the VM for guest OS interaction.2 For more information, see this Microsoft KB article.
		TCP	6167, 2500 to 33003	[For Microsoft SQL logs shipping] Port used by the runtime process on the VM guest OS from which Microsoft SQL logs are collected.
	Linux VM guest OS	TCP	22	Default SSH port used as a control channel.
	Linux VM guest OS	TCP	2500 to 33003	Default range of ports used as transmission channels during Linux file-level recovery and for Oracle log backup. For every TCP connection that a job uses, one port from this range is assigned.

1 Port 135 is optional to provide faster deployment.

2 If you use default Microsoft Windows firewall settings, you do not need to configure dynamic RPC ports: during setup, Veeam Backup & Replication automatically creates a firewall rule for the runtime process. If you use firewall settings other than default ones or application-aware processing fails with the "RPC function call failed" error, you need to configure dynamic RPC ports. For more information on how to configure RPC dynamic port allocation to work with firewalls, see this Microsoft KB article.

3 This range of ports applies to newly added backup infrastructure components. If you upgrade to Veeam Backup & Replication 10.0 from earlier versions of the product, the range of ports from 2500 to 5000 applies to the already added components.

Veeam U-AIR Connections

The following table describes network ports that must be opened to ensure proper communication of U-AIR wizards with other components.

From	To	Protocol	Port	Notes
U-AIR wizards	Veeam Backup Enterprise Manager	TCP	9394	Default port used for communication with Veeam Backup Enterprise Manager. Can be customized during Veeam Backup Enterprise Manager installation.

Azure Proxy Connections

From	To	Protocol	Port	Notes
Backup server/ Backup repository	Azure proxy	TCP	443	Default management and data transport port required for communication with the Azure proxy. The port must be opened on the backup server and backup repository storing VM backups. The default port is 443, but you can change it in the settings of the Azure Proxy. For details, see Specify Credentials and Transport Port

From

Protocol

Port

Notes

Backup server/ Backup repository

Azure proxy

TCP

443

Default management and data transport port required for communication with the Azure proxy. The port must be opened on the backup server and backup repository storing VM backups.

The default port is 443, but you can change it in the settings of the Azure Proxy. For details, see Specify Credentials and Transport Port

Azure Stack Connections

From	To	Protocol	Port	Notes
Backup server	Azure Stack	HTTPS	443, 30024	Default management and data transport port required for communication with the Azure Stack.

Proxy Appliance Connections (Restore to Amazon EC2)

From	To	Protocol	Port	Notes
Backup server/Backup Repository	Proxy appliance	TCP	22	Port used as a communication channel to the proxy appliance in the restore to Amazon EC2 process.
Backup server/Backup Repository	Proxy appliance	TCP	443	Default redirector port. You can change the port in proxy appliance settings. For details, see Specify Proxy Appliance.

Microsoft Active Directory Domain Controller Connections During Application Item Restore

The following table describes network ports that must be opened to ensure proper communication of the backup server with the Microsoft Active Directory VM during application-item restore.

From	To	Protocol	Port	Notes
Backup server	Microsoft Active Directory VM guest OS	TCP	135	Port required for communication between the domain controller and backup server.
		TCP, UDP	389	LDAP connections.
		TCP	636, 3268, 3269	LDAP connections.
		TCP	49152 to 65535 (for Microsoft Windows 2008 and newer)	Dynamic port range used by the runtime coordination process deployed inside the VM guest OS for application-aware processing1 For more information, see this Microsoft KB article.

1 If you use default Microsoft Windows firewall settings, you do not need to configure dynamic RPC ports: during setup, Veeam Backup & Replication automatically creates a firewall rule for the runtime process. If you use firewall settings other than default ones or application-aware processing fails with the “RPC function call failed” error, you need to configure dynamic RPC ports. For more information on how to configure RPC dynamic port allocation to work with firewalls, see this Microsoft KB article.

Microsoft Exchange Server Connections During Application Item Restore

The following table describes network ports that must be opened to ensure proper communication of the Veeam backup server with the Microsoft Exchange Server system during application-item restore.

From	To	Protocol	Port	Notes
Backup server	Microsoft Exchange 2003/2007 CAS Server	TCP	80, 443	WebDAV connections.
Backup server	Microsoft Exchange 2010/2013 CAS Server	TCP	443	Microsoft Exchange Web Services Connections.

Microsoft SQL Server Connections During Application Item Restore

The following table describes network ports that must be opened to ensure proper communication of the backup server with the VM guest OS system during application-item restore.

From	To	Protocol	Port	Notes
Backup server	Microsoft SQL VM guest OS	TCP	1433, 1434 and other	Port used for communication with the Microsoft SQL Server installed inside the VM. Port numbers depends on configuration of your Microsoft SQL server. For more information, see Microsoft Docs.

From

Protocol

Port

Notes

Backup server

Microsoft
SQL VM guest OS

TCP

1433,
1434 and other

Port used for communication with the Microsoft SQL Server installed inside the VM.

Port numbers depends on configuration of your Microsoft SQL server. For more information, see Microsoft Docs.

SMTP Server Connections

The following table describes network ports that must be opened to ensure proper communication of the backup server with the SMTP server.

From	To	Protocol	Port	Notes
Backup server	SMTP server	TCP	25	Port used by the SMTP server. Port 25 is most commonly used but the actual port number depends on configuration of your environment.

From

Protocol

Port

Notes

Backup server

SMTP server

TCP

Port used by the SMTP server.

Port 25 is most commonly used but the actual port number depends on configuration of your environment.

Veeam Backup Enterprise Manager Connections

Veeam Explorers Connections

Veeam Cloud Connect Connections

Veeam Agent for Microsoft Windows Connections

Veeam Agent for Linux Connections

Veeam Plug-ins for Enterprise Applications Connections

Internet Connections

If you use an HTTP(S) proxy server to access the Internet, make sure that WinHTTP settings are properly configured on Microsoft Windows machines with Veeam backup infrastructure components. For information on how to configure WinHTTP settings, see Microsoft Docs.

Used Ports Note:

Tenants cannot access Veeam Cloud Connect infrastructure components through HTTP(S) proxy servers. For information on supported protocols for Veeam Cloud Connect, see the Used Ports section in the Veeam Cloud Connect Guide.