Proxy Requirements (Storage Systems)

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-based 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:

[For Windows-based backup proxies] The Multipath I/O feature is enabled in the Windows Server Manager console. For more information, see Microsoft Docs.
[For Linux-based backup proxies] The multipath feature is configured on the proxy.
All ports of one proxy are in the same host group or initiator group on the storage system.
[For iSCSI] The necessary iSCSI targets are connected and multiple iSCSI sessions are established from the backup proxy to the storage system.
[For Fibre Channel] Zoning and masking on the FC switches and storage are configured.

iSCSI Protocol

[For Windows-based backup proxies] The proxy must have a Microsoft iSCSI Software initiator enabled.
[For Linux-based backup proxies] The proxy must have an Open-iSCSI Software initiator enabled.
For the majority of storage systems, Veeam Backup & Replication requests the storage system to create the iSCSI host automatically if Veeam Backup & Replication cannot find the host with the proxy server initiator IQN. If the host was not created, consult the storage-specific documentation for additional steps.
iSCSI traffic between the proxy and storage system must be allowed.

Note

Consider the following:

For storage rescan, Veeam Backup & Replication uses its own Veeam iSCSI initiator. The requirements for iSCSI initiators depend on the type of proxy used:

For Linux-based proxies deployed from JeOS ISO or for the Linux-based backup server that acts as a proxy, you must enable an Open-iSCSI Software initiator (iscsid).
For Microsoft Windows-based and Linux-based proxies that are not deployed from JeOS ISO, the Microsoft iSCSI Software initiator and Open-iSCSI do not need to be enabled.

For backup from storage snapshots, you must enable the Microsoft iSCSI Software initiator and Open-iSCSI.

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 LUNs of snapshots 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.
We recommend configuring the proxy on a physical machine.

NFS Protocol

NFS traffic between the backup proxy and storage system must be allowed.
[For Linux-based backup proxies] The backup proxy must have an NFS client enabled.

NVMe Protocol

The NVMe protocol can be used only with Linux-based backup proxies.
The NVMe-cli tool must be installed on the proxy.
For Veeam Backup & Replication to present NVMe namespaces of snapshots to the proxy, you must register the proxy with an NVMe Qualified Name (NQN) on the storage system.
The following technologies are supported: NVMe-RDMA, NVMe-FC and NVMe-TCP.
The following applies to NVMe-FC:

The proxy must have an NVMe-FC adapter installed and also access to the storage system over Fibre Channel fabric.
Install NVMe-FC devices on the proxy must be installed according to the vendor documentation. Ensure that the proxy operating system and the Fibre Channel adapter are compatible. Also, check that the WWN ID of the proxy is properly zoned on the Fibre Channel switch.