Veeam trying to connect to the wrong address

[dmitryk8]

Hello,
We have VBR 10.0.0.4461 P1 backuping several Hyper-V clusters. Each host in cluster has cluster interface (no access to production network), two SAN interfaces (no access to production network) and interface connected to production network. Veeam resides in production network. One day I noticed on firewall packets from Veeam to host's cluster and SAN IPs (445 port). I think that is not totally correct, so the question is how to prevent Veeam trying to connect to wrong addresses?

[Egor Yakovlev]

Hi Dmitriy.

Whatever IP Veeam gets from DNS for Hyper-V hostname(if its added by the name), will be used for management traffic.
There is also "Preferred networks" control that allows to force Veeam preferred connection in case multiple paths are available.

/Cheers!

[dmitryk8]

There are no records for that IPs in DNS. I have already added only production network in "Preferred networks", but it still tries to connect every ten minutes.

[Egor Yakovlev]

Well, attempts to poll host IP addresses is normal, even from other networks.
When you add Hyper-V host, Veeam collects all IPs of the host and periodically checks for connection to be aware of new paths available(say, tomorrow you decide to route all backup traffic via SAN Network interface). Also, we might attempt to connect to Hyper-V host shares to pick up some components(like backup indexing data), which also uses 445, however in this case we should use primary IP.
That shouldn't be something scary, but if you want to know the root you will have to troubleshoot logs(with Veeam support team if needed).