Feature Request - Advanced Networking Features (LACP & VLAN)

[tmckinnon]

Love the entire Veeam product suite so far and I'm while testing out recovery with VEB I've noticed that some advanced networking settings are missing from VER -

There's no option to setup a network team network interfaces nor options to assign VLAN tags to network cards so recovery from a SMB/VBR repository isn't possible without reconfiguring a switch.

Network teaming is out of the box with Windows 2012 R2, same with VLAN tags so this should be a doable feature.

[Dima P.]

Hi Travis,

Good request, though I am a bit surprised that it was not posted before. Thank you – we will look into this.

[Gostev]

There's no option to setup a network team network interfaces nor options to assign VLAN tags to network cards so recovery from a SMB/VBR repository isn't possible without reconfiguring a switch.

This sounds like something that should be set up on the OS level, as opposed to be handled by each individual application, no?

[Baptiste]

On my server, i can setup vlan directly on IDRAC for my network card then i can restore from VBR.

Regards,

[wyantis]

Was this ever implemented? I'm trying to recover to a server with LACP network, Not seeing any options to do anything other than very basic and simple network configuration.

[Nils]

Just wondering, given that LAG traffic distribution is by IP/L4-port hash (in best case), what's the point of running LACP with VER? Traffic from the repository uses just a single port anyway...

VAW would rather need to support L3 multipathing (as well as the storage) and then multiple ungrouped links would make (more) sense.