Hello,
The dual NIC has to live on the components that actually move data.
Per the Specifying Preferred Networks page, that list includes the gateway server, the VMware backup proxy, the backup repository. Veeam Backup & Replication server itself could also have a data-mover role (gateway for SMB/NFS, mount server, WAN accelerator host, or the integrated proxy and integrated repository inside the v13 Veeam Software Appliance). vCenter is not in that list - it only carries API traffic.
If you have a specific infrastructure environment, where not all of the interconnections are clear, I'd recommend consulting with Veeam Accredited Service Partners (VASP) or Veeam System Engineers.
Alternatively, you may want to contact your sales partner\account manager for assistance in finding a VASP in your region or for contracting Veeam System Engineers.
From your description, I may assume this setup, which is basically identical to the previous question:
Option 1 A HotAdd proxy per cluster with one vNIC in VLAN 100 and one in VLAN 500, a NIC in VLAN 500 on the repository (or its gateway server), and the VLAN 500 subnet added to Preferred Networks in VBR. The rule will direct the proxy-to-repo data movers onto VLAN 500 and fall back to VLAN 100 only if the preferred path cannot be established.
Option 2 (L3 routing) probably could work, but adds latency, firewall scope and complexity for no gain over a flat L2 backup VLAN.
NOTE: if you use Veeam Software Appliance all-in-one, with integrated proxy and integrated repository on the same VM, Preferred Networks has nothing inter-component to redirect because both data-mover endpoints are on the same host. You need at least one external proxy or external repository on VLAN 500 for the rule to actually shift traffic.
Veeam Software Appliance supports multiple network interfaces, configurable from the Veeam Host Management web UI or Text UI (TUI) in console (the TUI's "Advanced network" entry for VLANs, bonds and tunnels).
The dual NIC has to live on the components that actually move data.
Per the Specifying Preferred Networks page, that list includes the gateway server, the VMware backup proxy, the backup repository. Veeam Backup & Replication server itself could also have a data-mover role (gateway for SMB/NFS, mount server, WAN accelerator host, or the integrated proxy and integrated repository inside the v13 Veeam Software Appliance). vCenter is not in that list - it only carries API traffic.
If you have a specific infrastructure environment, where not all of the interconnections are clear, I'd recommend consulting with Veeam Accredited Service Partners (VASP) or Veeam System Engineers.
Alternatively, you may want to contact your sales partner\account manager for assistance in finding a VASP in your region or for contracting Veeam System Engineers.
From your description, I may assume this setup, which is basically identical to the previous question:
Option 1 A HotAdd proxy per cluster with one vNIC in VLAN 100 and one in VLAN 500, a NIC in VLAN 500 on the repository (or its gateway server), and the VLAN 500 subnet added to Preferred Networks in VBR. The rule will direct the proxy-to-repo data movers onto VLAN 500 and fall back to VLAN 100 only if the preferred path cannot be established.
Option 2 (L3 routing) probably could work, but adds latency, firewall scope and complexity for no gain over a flat L2 backup VLAN.
NOTE: if you use Veeam Software Appliance all-in-one, with integrated proxy and integrated repository on the same VM, Preferred Networks has nothing inter-component to redirect because both data-mover endpoints are on the same host. You need at least one external proxy or external repository on VLAN 500 for the rule to actually shift traffic.
Veeam Software Appliance supports multiple network interfaces, configurable from the Veeam Host Management web UI or Text UI (TUI) in console (the TUI's "Advanced network" entry for VLANs, bonds and tunnels).
Statistics: Posted by vnikiforov — May 19, 2026 9:57 am
