Multiple networks: Issue forcing backup to use faster path.

[TimLawhead]

Case #05902250

I've got a new physical hardened linux repo and tape library with 25G connections. The Virtual environment is using the 25G switches for storage and vMotion traffic. I added a port group to the virtual switches that were running the vMotion and storage iSCSI traffic. I create a NIC on those vSwitches for the VM proxy and am looking to push the backups over the same storage 25G connection.

I created a new backup to target a single VM on host 1 and pointed it to the hardened linux repo. The job took @5 minutes and didn't use the 25G network path. I then set the proxy server VM to use the Preferred Networks of the 192.1.1.0/24 and 192.1.2.0/24, and kicked the job off. Watching the activity on the proxy server, I can see it never uses the 25G NICs and the job went from @5 minutes to @20 minutes to complete.

I'm pretty sure there's an issue with the VBR server being able to understand the path and maybe I need to remove the Repo from Veeam and add it back in using only the other path... which I assume would require also adding NICs on the 25G switches to the VBR server VM. I think there may be some other moving parts and best practices needed to get this working efficiently.

Anyone dealt with this type of setup and got it sorted out?

TIA

[JailBreak]

Hi,

I always set my Veeam server to use preference networks to use the Storage Network, or dedicated Backup Network. This always work, only when the network is not reachtable, it will use other network.

Do not forget to use preference networks, all devices(Veeam Servers, Proxys etc.) need to have this network set always need to have connection from the source to the destination.

Check the full path and see if all devices are reachable to and in that network.