Balance backup traffic across multiple repo Nics

[collinp]

Is there a way to balance backup traffic across 2 nics on a repository server without lacp and load balancing? Here is the sample scenario:

1) Hyper-v Job #1 backs up vm's on Hyper-v 1 host with host IP of 192.168.100.1 using on-host proxy mode
2) Hyper-v Job #2 backs up vm's on Hyper-v 2 host with host IP of 192.168.100.2 using on-host proxy mode
3) Repository Server has 2 x 1Gbps nics with IP's of 192.168.100.3 and 192.168.100.4
4) Cannot use lacp or any type of load balancing
5) You start Hyper-v Job #1 and it uses repo nic 192.168.100.3
6) 5 minutes later you start Hyper-v Job #2. Which repo nic will it use - 192.168.100.3 or 192.168.100.4?

And if there isn't a way for Veeam to load balance across the 2 Repo nics because it is done at a windows level, can routes be added like below? If so, what servers do the routes need to be created on and is this syntax correct?

route -p add 192.168.100.1 mask 255.255.255.255 gw 192.168.100.3 if 1 #Make Hyper-v Host 1 choose repo interface 1
route -p add 192.168.100.2 mask 255.255.255.255 gw 192.168.100.4 if 2 #Make Hyper-v Host 2 choose repo interface 2

Future test question?

Collin

[Egor Yakovlev]

Hi Collin,

You can add same repository twice using different IP addresses for static traffic split.
I assume you are using Windows type of repository, then here is an example setup:
- add Repository01(D:\Backups01) with 192.168.100.3
- add Repository02(D:\Backups02) with 192.168.100.4
- Target HV01 jobs to Repository01, Target HV02 jobs to Repository02
Veeam will use respectful IP addresses\NICs they belong to.

For dynamic balancing you will have to play with DNS resolution(add single Repository and control which IP Veeam gets each time job starts).

/Cheers!