Proxy Requirements
This section describes requirements for proxies used for storage integration.
General Requirements
- For VMware integration
- You must assign to a Microsoft Windows or a Linux machine the role of a backup proxy. This can be a dedicated machine or backup server performing the role of the default backup proxy.
- We recommend that you add only one proxy to one initiator group. Otherwise, you may encounter issues on proxies with the number of devices that correspond to storage snapshot clones. During the backup process, devices may be unintentionally created on all proxies added to the initiator group, for example, if two backup jobs that use proxies from the initiator group work simultaneously. The created devices may be accumulated.
- For backup from storage snapshots, the transport mode for VMware backup proxy must be set to Automatic selection or Direct storage access.
- For backup from storage snapshots, access to the production volumes or LUNs is not required. The backup proxy only accesses the snapshot/clone of the production datastore to read the data.
During backup, Veeam Backup & Replication creates a temporary snapshot of the production volume and then mounts it to the backup proxy. Therefore the backup proxy does not interact with the production volume or LUN, and mapping to the production volume is not required. For more information on how backup from storage snapshots works, see Backup from Storage Snapshots.
- For Linux backup proxy, to check compatibility with a storage system, see the system requirements provided by the storage system vendor.
- The proxy and the storage system must support the same IP version.
- [For Veeam Agent and NAS integration] Check requirements for the general-purpose backup proxy. For more information, see the General Purpose-Backup Proxy section in the Veeam Backup & Replication User Guide
- If you want to configure multipathing (MPIO) feature for backup from storage snapshots, check the following requirements:
- [For Windows-based backup proxies] The Multipath I/O feature must be enabled in the Windows Server Manager console. For more information, see Microsoft Docs.
- [For Linux-based backup proxies] The multipath feature should be configured on the proxy.
- All ports of one proxy must be in the same host group or initiator group on the storage system.
- Zoning and masking on the FC switches and storage must be configured.
iSCSI Protocol
- [For Microsoft Windows] The proxy must have a Microsoft iSCSI Software initiator enabled.
- [For Linux] The proxy must have an Open-iSCSI Software initiator enabled.
- iSCSI traffic between the proxy and storage system must be allowed.
Note |
For storage rescan, Veeam Backup & Replication uses its own initiator. For this reason, a Microsoft iSCSI Software initiator and Open-iSCSI may not be enabled when you perform storage rescan. For backup from storage snapshots, however, the Microsoft iSCSI Software initiator and Open-iSCSI must be enabled. |
SMB (CIFS) Protocol
SMB (CIFS) traffic between the proxy and storage system must be allowed.
Fibre Channel Protocol
- The proxy must have a Fibre channel adapter installed and must have access to the storage system over Fibre Channel fabric.
- To let Veeam Backup & Replication present snapshots of LUNs to the proxy, you must register the proxy with a WWN ID on the storage system.
- Fibre Channel devices must be properly installed on the proxy. For example, see the vendor documentation and check that the proxy OS and the Fibre Channel adapter are compatible. Also, check that the WWN ID of the proxy is properly zoned on the Fibre Channel switch.
NFS Protocol
- NFS traffic between the backup proxy and storage system must be allowed.
- [For Linux] The backup proxy must have an NFS client enabled.