Help for network design

[matteu]

Hello,

I would like to have your advice about my design.

I have 1 server VLAN 10G and 1 backup VLAN 10G.
However, when I want to transfert data between both VLAN, today it's on 1G because of hardware between them.

My idea is :

1 VBR VM on Hyper-V on Server VLAN + Backup
2 Hyper-V
1 Linux hardened repository physical server on Server VLAN + Backup VLAN
1 NAS on Backup VLAN

My idea is to add the Linux Hardened repository with it's Server VLAN IP (based on DNS)
Execute backup on the Server VLAN with throtle limit
Execute backup copy on the Backup VLAN

For this, I need to have on my linux physical server 1 teaming with 2 network interface on different VLAN.

What do you think about it ?

[Andreas Neufert]

You can set preferred network to handle Veeam to Veeam communication.
In this case communication between OnHost Hyper-V and the hardened repository server can be done. Between the NAS gateway and the NAS system it only follows regular networking and no Veeam rule is used.

You can set traffic rules in Veeam between Veeam IP addresses (set in both directions). Please do not set them on the Repository wizard itself.

So the Veeam porcessing is with this pretty clear.

In case of linux physical server NIC teaming, do I get it right that you want to add both cards to both vlans with virtual IP addresses?

[matteu]

Thanks for your answer.

Are you sure preferred network will be needed here ? Because Veeam server and Hyper-V network will be on the same VLAN so they should use this network first right ?
NAS Gateway will be the VBR server itself on this case.

Throttle is because there is no dedicated NIC on Hyper-V server and I don't want backup break production because of network traffic.

On the linux, I will have only 1 card with 2 port 10G. So I will make a teaming active / passive (storage will not be able to handle 2x10G...). On this teaming, I'm thinking about create 2 virtual interface : 1 on the server vlan and the other on the backup vlan yes.
I will need to configure the network switch port to allow both VLAN and then set on each virtual interface their corresponding VLAN.

[Andreas Neufert]

OK so dataflow will be

Hyper-V host on Server VLAN => Hardened Repository on Server VLAN
then BCJ
Hardened Repository Server on first found VLAN to Veeam Server acting as storage gateway (first found VLAN) then from there over the Backup VLAN to the NAS system on Backup VLAN.

You need to set a preferred network to force Veeam to work at the backup copy job over the specific network and not on the first found one.

For the Backup traffic throttling you need to define an IP address to IP address network rule and set throttling there (don´t go too low on throughput) and set the rule in the opposite direction in the same way.

For the team bounding, I would potentially avoid this, as inward and outward traffic would go from both VLANs over the same NIC. As well teaming is a source of errors when you can not really need it in a disaster. So I would just go and use both NIC ports in different VLANs without teaming.

[matteu]

Thanks for your answer.
I understand all and I agree except the last point.

I have to choose between high availability or dedicate a nic port.

I always use HA on my installation but never with 2 IP. It works fine.