Feature request - Backup Copy routing using multiple NICs

[sdolcourt]

Case 08077935

Veeam does not natively offer a means to configure a backup copy job (or any other flow) via a wizard or setting, to specifically use a subnet or interface. Veeam only offers global network traffic rules that apply to all flows.

Our scenario is two geographically separeted datacenters, which are linked by several difference network routes / circuits. Local traffic is moved on production 10 net, and we have been given a 172 subnet dedicated for DC <-> DC traffic. Goal is to send backup copy traffic from local to remote repo along this 172 net link.

There is no difficulty to configure 2 interfaces on any Veeam component, so Window VBR, and local and remote hardended repos have intefaces for 10 (local) and 172 (remote) net. I have added the remote repo in local VBR with the 172 net IP address, and configured static routing for the 172 net on all 3 systems.

However, due to various logic holes in our nework's routing, I cannot guarantee that Veeam BCJ routes along the 172 net, from the local repo to the remote repo. I would be able to guarantee that flow, if the Veeam network traffic rules, or flow parameters within the backup copy job creation wizard, did so.

I would like to see something as simple as "choose a different NIC or subnet to send data" when creating a backup copy job. Or, in the global traffic rules, when setting a throttling paramter, a checkbox that says "apply to backup copy traffic only", and I can then use source and destination 172 net IP paramteres to specify that flow.