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.

[david.domask]

Hi sdolcourt,

Thank you for the ideas, your situation is understood and will discuss internally. However, a few questions on what was discussed in the case.

1. Preferred networks: I see it was suggested, but seems there is doubt it will work as you expect it to. As I get it all the local Veeam components will have two interfaces, and main idea is just for the backup copy jobs (BCJ) ensure that it goes over the 172 network; I expect Preferred Networks ought handle this just fine, and if it's not working as expected it should be investigated in a Support Case

2. WAN Accelerators: Backup Copy Jobs let you specify the data path settings, and WAN Accelerators may assist here; it's additional roles to install to your infrastructure, but it would let you be very specific with the networks the WAN accelerator has access to.

[sdolcourt]

Hi, David,

Thank you.

I do see incrementing Tx numbers on the network link we're using for BCJ, so I *think* the expected commuincation path is working. I'll ask our networking hyenas to let me know.

As is the standard IT answer, it depends... If the preferred 10 net is able to route within our network to get to remote 172 net, then yes, correct. However, at some of our sites, the hyenas disable this routing due to separating traffic amonst the several iDMZs, where some iDMZs are not to talk to others: ITAR/DFARS/CUI, and the like. Thus the benefit for the application to assign the flow, and BCJ can flow down its assigned path.

I didn't know that WAN accelerators could do this, good to know and have this in mind. You're right, it does mean additional roles. Definitely I'm lobbying that a checkbox / wizard that is native to the VBR app to enable interface / subnet selection is a better solve than having to stand up more infrastructure.