Backup
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.
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 | Required to deploy a 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 http://support.microsoft.com/kb/929851/en-us. | ||
TCP | 6167, 2500-5000 | [For Microsoft SQL Server transaction logs shipping.] 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 http://support.microsoft.com/kb/929851/en-us. |
Log shipping server | TCP | 2500 - 5000 | [For Microsoft SQL Server transaction logs shipping.] Default port range 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. Veeam Backup & Replication automatically creates a firewall rule for the runtime process during the installation. If you use firewall settings other than the default ones or application-aware processing fails with the “RPC function call failed” error then, you need to configure dynamic RPC ports manually.
Restore
The following table describes network ports that should be opened during the application-item restore.
From | To | Protocol | Port | Notes |
|---|---|---|---|---|
Machine running Veeam Explorer (this can be Veeam backup server or standalone console) | Target remote machine and/or staging Microsoft SQL server | TCP, UDP | 135, 445 | Required to deploy a runtime coordination process on a target guest OS. |
TCP | 49152-65535 (for Microsoft Windows 2008 and later) | Dynamic RPC port range used by the runtime coordination process deployed on a target guest OS. For more information, see http://support.microsoft.com/kb/929851/en-us. | ||
Microsoft SQL Server VM guest OS | TCP | 1433,1434 and other | Used for communication with the Microsoft SQL Server installed inside the VM during the application-item restore. Exact port numbers depend on the configuration of your Microsoft SQL server. To learn more, see http://msdn.microsoft.com/en-us/library/cc646023.aspx#BKMK_ssde. | |
UDP | 1434 | Used by Microsoft SQL Server Browser Service. To learn more, see https://technet.microsoft.com/en-us/library/ms181087(v=sql.130).aspx. | ||
TCP | 1025 - 1034 | Default RPC port range for the runtime component installed on target or staging server guest OS to support restore operations in most scenarios. Port is open only during application item restore (Veeam Explorer session). To learn how to modify default port range, see How Veeam Explorer for Microsoft SQL Server Works. | ||
Target remote machine to which application items are restored, | Mount server associated with the backup repository | TCP | 3260 - 3270 | Range of ports opened by Veeam Backup & Replication for iSCSI traffic during restore to the original VM. See Mount Operations for details. Ports are open only during application item restore (Veeam Explorer session). |
