Veeam Agent uses more Networkcard

[BackupTest]

Hello,
today we found out that the agent uses all networkcards on the host ( 3 networkcards ) to send the Backup to a LAN target.
Is there a regestry key, to tell use only that nic ?
or any other solution to bind the Agent to one networkcard?

Thanks for Help.

[Dima P.]

Hello and welcome to the community BackupTest,

Can you please double check the actual network usage in resource monitor? Agent should use only one network interface to connect with backup repository, all other activity might be related to the component communication over the network socket. Thanks!

[Vitaliy S.]

As Dima said Veeam Agent will use only one network card to access the backup repository, however you can make edits to the hosts file on the Agent to make sure that backup traffic goes through the required NIC (given that all NICs might have access to the repository).

[BackupTest]

I have opend a Support case for that.
Yes Veeam Agent uses only one networkcard on Windows Server 2008 R2.
an No on Windows Server 2012 r2 ans Windows Server 2016 .
In the Support Case i have posted a video of that.

I think it's the best software nic teaming i have ever seen in my live. <--- and thats true
but we have to saperate the Networks, one for backup and one for production.
Thats why the servers had two networkcards.

On Windows Server 2008 R2 it works like it should production is for production and backup is for backup.

[Dima P.]

BackupTest,

If possible, please share the case ID. Thanks!

[BackupTest]

Hello,
The Case ID is Case # 03321443.

[BackupTest]

Take a look at the added video.

This issue is more a feature than an issue.

a) Best nic teaming i have ever seen
b) incredible backupspeed.

You should implement this as a feature it makes the agent the fastest and best backuptool ever.

You should take this as an option in the Veeam Agent for Windows/Linux 3.0 and let the user decide.

My idea is.

NIC Selection Option
=================

[ ] use all nics that can reach the share | <- userfrendly and easy to understand
[ ] NIC 1 ( Development ) | <- multible selection
[ ] NIC 2 ( Production ) | <- multible selection
[ ] NIC 3 ( Backup ) | <- multible selection

Please let your senior engineers know this, that this is a great feature.

I wish you a Mary Christmas and a happy new year

and please don't stop to improve the best backup agent ever.

maybe you could tell me the thoughts of your senior engine at my thoughts.

[BackupTest]

Hello,
today i found a workaround to bind the Networktraffic back to on networkcard.

https://blogs.msdn.microsoft.com/emberg ... tichannel/

now my backup network is forced for the backupserver,
but all smb trafic to and from the backupserver runs now over the backupnetwork. <-- And for a workaround i think thats okay.

and on more with more descriptions.
https://www.thomasmaurer.ch/2013/08/hyp ... tichannel/

[Dima P.]

Hi BackupTest,

Thanks for the detailed review. I've shared it with the R&D team. Happy holidays to you too!

[hyvokar]

Hi,

is there any news on this feature?

I have 5 nics on my win10 workstation and would like to use more then one for backups.

[Dima P.]

Hello hyvokar,

Unfortunately, Veeam Agent still utilize only one network adapter, but I'll add your feedback to this feature request. Thanks!

[hyvokar]

Thanks Dima!
In my case, this would also require some changes on VBR side.

I have three dedicated VLANS and subnets for backups (VLANS 110,111,112, subnets 192.168.110.0 192.168.111.0 192.168.112.0) . So in order to this to work, VBR should be able to receive traffic in more than one interface and in Veeam Agent, there should be an option to add optional IP addresses to use for backup server.


Currently full backup on my workstation takes 30 hours using only one 1gb nic.