We've recently upgraded our connection between two office locations from single to dual gigabit, and now I'm trying to make use of this for backup.
- 2 ESXi hosts (5.1)
virtual proxy (Win2012R2) with direct SAN access through ESXi storage NICs (wasn't too happy with hotadd in Veeam 8)
- Veeam Backup server (Win2008R2, VBR 9.0u2), local backup repository (DAS)
What I did:
- added a 2nd NIC to the backup server, added 2nd IP address (B) to already existing IP (A) in server subnet
added a 2nd vNIC to the proxy, bound both vNIC to dedicated host NICs through extra port groups with a single NIC, added 2nd IP (D) to already existing IP (C) in server subnet
the new IP addresses were selected to vary traffic distribution over the trunk: B=A+1, D=C+3
verified that traffic distributes over both LACP links and both ESXi NICs when using different connection combinations A-B, A-C, B-C, and B-D
the setup uses DNS names for the repository and the proxy, so I added 2nd IP addresses to the server's and the proxy's DNS records
verified that both IP addresses are resolved in turn through DNS (round robin with Windows 2012R2 DNS server)
However, when running a backup job, only one ESXi NIC and one backup server NIC are ever used (at 100% load), the new ones are idle. All visible connections are A-B. The job has several dozen vDisks, parallel processing is on. iSCSI multipathing on the proxy works fine.
Experimentally, I've tried adding static routes for A-C, B-D / C-A, D-B on each side. This had no effect.
How do I get Veeam proxy/repository to rotate through the source/destination addresses?