I have no Case ID because I already fixed it for now. But I have a very strange behavior, I even do not know if it is Veeam or just Windows, and I wanted to share with you and see if anyone has the same problem or maybe has a better solution.
My setting: our Veeam B&R Server is a dedicated hardware server. We have 3 active nics: Nic1 is in NetworkA, Nic2 is in NetworkB (managementNetwork), and Nic3 is directly attached to the backup storage. All nics are 10G, and 10G is working fine.
Now we have a test SQL server where we regularly refresh the database by restoring a live SQL DB via Veeam to the test server. Test server has one Nic in NetworkA, also 10G. So normally I would say the restore would just use the Nic1 of the B&R Server because it is the most direct way. But Veeam is using NetworkB, so the traffic gets routed through our firewall which only can do 1G.
To change this behavior, I tried the following:
- added a route for traffic to the IP of the test server over NIC1 with a lower metric (the routing was already okay, tracert would not use the firewall) - did not help
- created a firewall rule: block outgoing traffic from Nic2 to NetworkA to force the use of Nic1 in case of traffic in direction of NetworkA - did not help
- created a firewall rule: block incoming traffic from NetworkA to Nic2 - now it works (only in combination with the outgoing rule)
Am I the only one with a problem like this? Any insights on how to change this behavior wihtout these firewall rules?
Thanks!