Which of the following ports needs to be open between servers replicating by using storage replica to allow SMB direct traffic?
On backup infrastructure components, Veeam Backup & Replication automatically creates firewall rules for the required ports. These rules allow communication between the components. Show
You can find the full list of the ports below. Microsoft Windows Server 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 section. The Microsoft Windows server that acts as an NFS file share requires network ports listed below and also ports listed in the NFS Backup Repository. The Microsoft Windows server that acts as an SMB file share requires network ports listed below and also ports listed in the SMB Backup Repository.
1 This range of ports applies to newly installed Veeam Backup & Replication starting from version 10.0, without upgrade from previous versions. If you have upgraded from an earlier version of the product, the range of ports from 2500 to 5000 applies to the already added components. Linux Server 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 Microsoft Windows/Linux-based Backup Repository section. The Linux server that acts as an NFS file share requires network ports listed below and also ports listed in the NFS Backup Repository. The Linux server that acts as an SMB file share requires network ports listed below and also ports listed in the SMB Backup Repository.
1 This range of ports applies to newly installed Veeam Backup & Replication starting from version 10.0, without upgrade from previous versions. If you have upgraded from an earlier version of the product, the range of ports from 2500 to 5000 applies to the already added components. Backup Server The following table describes network ports that must be opened to ensure proper communication of the backup server with backup infrastructure components.
Backup & Replication Console The following table describes network ports that must be opened to ensure proper communication with the Veeam Backup & Replication console installed remotely.
1 This range of ports applies to newly installed Veeam Backup & Replication starting from version 10.0, without upgrade from previous versions. If you have upgraded from an earlier version of the product, the range of ports from 2500 to 5000 applies to the already added components. Backup Proxy The following table describes network ports that must be opened to ensure proper communication of backup proxies with other backup components.
1 Port 135 is optional to provide faster deployment. 2 This range of ports applies to newly installed Veeam Backup & Replication starting from version 10.0, without upgrade from previous versions. If you have upgraded from an earlier version of the product, the range of ports from 2500 to 5000 applies to the already added components. Backup Repositories
Microsoft Windows/Linux-based Backup Repository 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.
1 This range of ports applies to newly installed Veeam Backup & Replication starting from version 10.0, without upgrade from previous versions. If you have upgraded from an earlier version of the product, the range of ports from 2500 to 5000 applies to the already added components. NFS Backup Repository The following table describes network ports that must be opened to ensure proper communication with NFS shares added as backup repositories.
SMB Backup Repository The following table describes network ports that must be opened to ensure proper communication with SMB (CIFS) shares added as backup repositories.
1 Port 135 is optional to provide faster deployment. Dell EMC Data Domain System For more information, see Dell EMC Documents.
ExaGrid
HPE StoreOnce
Quantum DXi
Object Storage Repository The following table describes network ports and endpoints that must be opened to ensure proper communication with object storage repositories. For more information, see Object Storage Repository.
External Repository The following table describes network ports and endpoints that must be opened to ensure proper communication with external repositories. For more information, see External Repository.
Archive Object Storage Repository The following table describes network ports and endpoints that must be opened to ensure proper communication with object storage repositories used as a part of Archive Tier. For more information, see Archive Tier.
Storage Systems
Dell EMC VNX(e) Storage
Dell EMC Isilon Storage
HPE 3PAR StoreServ Storage
HPE Lefthand Storage
HPE Nimble Storage
IBM Spectrum Virtualize Storage
NetApp Data ONTAP Storage
Universal Storage API Integrated System The following tables describe network ports that must be opened to ensure proper communication with Universal Storage API integrated systems:
DataCore SANsymphony
Dell EMC SC Series/Compellent
Fujitsu ETERNUS DX/AF
INFINIDAT InfiniBox
NetApp SolidFire/HCI
Pure Storage FlashArray
Tintri IntelliFlash/Western Digital/Tegile
Gateway Server The following table describes network ports that must be opened to ensure proper communication with gateway servers.
1 Port 135 is optional to provide faster deployment. Tape Server The following table describes network ports that must be opened to ensure proper communication with tape servers.
1 This range of ports applies to newly installed Veeam Backup & Replication starting from version 10.0, without upgrade from previous versions. If you have upgraded from an earlier version of the product, the range of ports from 2500 to 5000 applies to the already added components. WAN Accelerator 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.
1 This range of ports applies to newly installed Veeam Backup & Replication starting from version 10.0, without upgrade from previous versions. If you have upgraded from an earlier version of the product, the range of ports from 2500 to 5000 applies to the already added components. Guest Interaction Proxy Connections with Non-Persistent Runtime Components The following tables describe network ports that must be opened to ensure proper communication of the backup server and backup infrastructure components with the non-persistent runtime components deployed inside the VM guest OS for application-aware processing and indexing.
Network ports described in the table below are NOT required when working in networkless mode over VMware VIX/vSphere Web Services.
Connections with Persistent Agent Components The following table describes network ports that must be opened to ensure proper communication of the backup server with the persistent agent components deployed inside the VM guest OS for application-aware processing and indexing.
Log Shipping Components The following tables describe network ports that must be opened to ensure proper communication between log shipping components.
Log Shipping Server Connections
MS SQL Guest OS Connections
Oracle Guest OS Connections
CDP Components The following table describes network ports that must be opened to ensure proper communication of Veeam CDP components with other backup components.
Recovery Components
Guest OS File Recovery The following table describes network ports that must be opened to ensure proper communication between components for guest OS file recovery.
Mount Server Connections
Helper Appliance Connections
Helper Host Connections
Guest OS Connections
Veeam vPower NFS Service
1 This range of ports applies to newly installed Veeam Backup & Replication starting from version 10.0, without upgrade from previous versions. If you have upgraded from an earlier version of the product, the range of ports from 2500 to 5000 applies to the already added components. SureReplica Recovery Verification
Veeam U-AIR The following table describes network ports that must be opened to ensure proper communication of U-AIR wizards with other components.
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.
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.
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.
Proxy Appliance (Restore to Amazon EC2, Google Cloud)
Azure Proxy
Azure Helper Appliance
Azure Stack
Veeam Backup Enterprise Manager Veeam Backup Enterprise Manager Connections Veeam Explorers
Veeam Cloud Connect Veeam Cloud Connect Connections Veeam Agents Veeam Agent for Microsoft Windows
Veeam Agent for Linux
Veeam Agent for Mac
Veeam Plug-ins for Enterprise Applications
Veeam Plug-ins for Cloud Solutions
Kasten K10 Kasten K10 Connections Other Connections NDMP Server The following table describes network ports that must be opened to ensure proper communication with NDMP servers.
SMTP Server The following table describes network ports that must be opened to ensure proper communication of the backup server with the SMTP server.
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.
Which storage replication mechanism is used by Windows Server in multi site failover cluster?Storage Replica is Windows Server technology that enables replication of volumes between servers or clusters for disaster recovery. It also enables you to create stretch failover clusters that span two sites, with all nodes staying in sync.
How do I replicate one server to another?Step 1: Install and configure Windows Admin Center on your PC. ... . Step 2: Provision operating system, features, roles, storage, and network. ... . Step 3: Set up server-to-server replication. ... . Step 4: Manage replication.. How do I enable replication on my server?Right-click the selected virtual machine and click Enable Replication to open the Enable Replication wizard. On the Before you Begin page, click Next. On the Specify Replica Server page, in the Replica Server box, enter either the NetBIOS or FQDN of the Replica server.
|