Hi ​@TK515 -

Have you looked at the Network Rules section in the User Guide?

https://helpcenter.veeam.com/docs/backup/vsphere/network_rules.html?ver=120

In the Veeam Console, from the Main Menu, select Network Traffic Rules and add your Rule. Sounds like you need to create a Preferred Network of your Backup environment:

https://helpcenter.veeam.com/docs/backup/vsphere/select_backup_network.html?ver=120

Hope that helps.

Also...though a bit different, someone had some issues getting traffic over a specific (10Gb) NIC and ended up needing to add IPs of them to host profiles on the Proxy. To understand a real-world situation with traffic path, may be worth a read through all the comments

Thanks! I did configure the preferred network to use the 25gb vlan that the exagrid repository are on. Im monitoring now and based on times it appears they must be using the 25gb ports and not the 1gb management port. On monday I will remove the selection to use the 1gb port for backups just to make sure everything is working the way I want it.

Sounds good. Keep me posted. Have a good weekend.

Thanks! You too!

From my point of view is better to register exagrid in veeam console under dns, which is resolving 172.16.30.x ip.

FQDN under is registered in veeam console, is primary ip under which is trying to connect. If this is not working, then is trying to connect to any other interface.

If you have more commponents and they have no interface with this subnet 172.16.30.x, then backup will be time-outed, because such interface is not on proxy servers or repositories. And after first timeout they will be used under they IP as fqdn is resolving them.

So my suggestion is to correct dns for exagrid as best solution ...

Hi ​@TK515 consider all Veeam components must have proper connectivity on the Preferred Networks. Otherwise, Veeam try to use all usable networks with a sensible slow down job initialization, backup performances are reduced. All of this needed a network design organized and secured.