Hi
Looking for some advice on throttling affecting my Hyper-v servers. Each server has 2 nics one a 172.30.125.1/24 range for management and another on 172.1.8.1/23 for backups this is set as a prefered network in VBR (version 10 btw).
The Hyper-v servers are added to veeam via their DNS entry so on the management network. I did apply the KB so veeam sees all nics on the Hyper-v server https://www.veeam.com/kb3140
When I apply a network throttle to the 172.30.125.1/24 range it also affects servers backing up over the prefered network. Is this the case because the Hyper-v hosts are added over their DNS being on the management IP range?
Any advice greatly appreciated thanks.
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Dec 14, 2021 7:31 am
- Full Name: Mark Smith
- Contact:
-
- VP, Product Management
- Posts: 7081
- Liked: 1511 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Throttling affecting Prefered Network
No, it should not affect the processing or the other IP ranges.
Does the Veeam Repository Server has as well 2 IPs in the different subnets?
Did you performed the rescan as outlined in the KB?
Can you maybe draw something to understand which IP addresses are bound to what interfaces and how they interact with each other?
As well a screenshot of the preferred network and throttling rules would help I guess.
Does the Veeam Repository Server has as well 2 IPs in the different subnets?
Did you performed the rescan as outlined in the KB?
Can you maybe draw something to understand which IP addresses are bound to what interfaces and how they interact with each other?
As well a screenshot of the preferred network and throttling rules would help I guess.
-
- Veeam Software
- Posts: 3626
- Liked: 608 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Throttling affecting Prefered Network
Hello,
@marksmithesg I agree with Andreas, the behavior is not expected and must be treated as a technical issue. Therefore, one more useful step will be to open a support case. Please share a support case ID over here.
Thanks!
@marksmithesg I agree with Andreas, the behavior is not expected and must be treated as a technical issue. Therefore, one more useful step will be to open a support case. Please share a support case ID over here.
Thanks!
Who is online
Users browsing this forum: No registered users and 12 guests