This document is not maintained any longer.Configuring Required Ports
The following table describes network ports that must be opened to ensure proper communication with the runtime coordination process deployed inside the Microsoft SQL Server guest OS for application-aware processing and transaction logs shipping of SQL Server VM.
From | To | Protocol | Port | Notes |
|---|---|---|---|---|
Veeam backup server or Guest interaction proxy (in Enterprise and Enterprise Plus editions) |
Microsoft SQL Server VM guest OS | TCP, UDP | 135, 137-139, 445 | Ports required to deploy the runtime coordination process on the VM guest OS. |
TCP | 49152-65535 (for Microsoft Windows 2008 and newer) | Dynamic RPC port range used by the runtime coordination process deployed inside the VM guest OS for application-aware processing (when working over the network).* For more information, see this Microsoft article. | ||
TCP | 6167 | [For Microsoft SQL Server transaction logs shipping.] Port used by the runtime process on the VM guest OS from which transaction logs are collected. | ||
Microsoft SQL Server VM guest OS | Veeam backup server or Guest interaction proxy (in Enterprise and Enterprise Plus editions) | TCP | 49152-65535 (for Microsoft Windows 2008 and newer) | Dynamic RPC port range used by the runtime coordination process deployed inside the VM guest OS for application-aware processing (when working over the network).* For more information, see this Microsoft article. |
Log shipping server | TCP | 2500 - 5000 | [For Microsoft SQL Server transaction logs shipping.] Default range of ports used by Veeam data mover service for data transmission over the network. | |
Log shipping server | Backup repository | TCP | 2500 - 5000 | [For Microsoft SQL Server transaction logs shipping.] Default range of ports used by Veeam data mover service for data transmission over the network. |
* - 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.