Comprehensive data protection for all workloads
Post Reply
bunger
Expert
Posts: 145
Liked: 10 times
Joined: Jun 23, 2010 5:39 pm
Full Name: Bill Unger
Contact:

Traffic Management Doesn't seem to be working

Post by bunger »

We are running Veeam B&R v9.0.0.1491 and are replicating the nightly backups to an offsite repository.

Because that replication could sometimes spill into the work day, I have created a traffic management configuration in Veeam to throttle bandwidth to 2Mbps M-F 7am-5pm. The settings for this are as follows:
Source range: 192.168.74.19 - 192.168.74.19
Target range: 192.168.140.6 - 192.168.140.6
Action: throttle network traffic
Throttle to: 2Mpbs
During these specific time periods: ( I have selected Mon-Fri, 7am-5pm )

However, I am noticing the communications between the 2 devices for which I have set that throttle are utilizing 5Mpbs during those hours. Our firewall can show live traffic stats and the link between 74.19 and 140.6 is pegged at 5Mbps ( which is basically the upload cap for the 74.19 location ). Details for the traffic show 5 connections from 74.19 to 140.6 on port 6165 and each of the 5 are utilizing 1Mbps.

Does the traffic management setting in Veeam only apply on a per connection basis, or should it be throttling all connections to a cumulative 2Mpbs?
PTide
Product Manager
Posts: 6408
Liked: 724 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Traffic Management Doesn't seem to be working

Post by PTide »

Hi,
<...>or should it be throttling all connections to a cumulative 2Mpbs?
This. Throttling is global so I think that you should contact support team on that issue. Please don't forget to post your case ID.

Thanks
Gostev
Chief Product Officer
Posts: 31457
Liked: 6648 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Traffic Management Doesn't seem to be working

Post by Gostev »

Also, please keep in mind that traffic throttling is applied between Veeam's source and target data movers only.
bunger
Expert
Posts: 145
Liked: 10 times
Joined: Jun 23, 2010 5:39 pm
Full Name: Bill Unger
Contact:

Re: Traffic Management Doesn't seem to be working

Post by bunger »

The source and target IPs in the traffic rule are the source and target data movers.
skrause
Veteran
Posts: 487
Liked: 105 times
Joined: Dec 08, 2014 2:58 pm
Full Name: Steve Krause
Contact:

Re: Traffic Management Doesn't seem to be working

Post by skrause »

He means that the data mover services are all it throttles. If there is other traffic (SMB, HTTP, etc) between the hosts on those IP addresses then that will not be counted.
Steve Krause
Veeam Certified Architect
bunger
Expert
Posts: 145
Liked: 10 times
Joined: Jun 23, 2010 5:39 pm
Full Name: Bill Unger
Contact:

Re: Traffic Management Doesn't seem to be working

Post by bunger »

The traffic that is exceeding the rule is flowing through port 6165, which is described as the default port used for data transfer between WAN accelerators.
Gostev
Chief Product Officer
Posts: 31457
Liked: 6648 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Traffic Management Doesn't seem to be working

Post by Gostev »

WAN accelerators currently don't respect this settings, only data movers aka Direct mode.
bunger
Expert
Posts: 145
Liked: 10 times
Joined: Jun 23, 2010 5:39 pm
Full Name: Bill Unger
Contact:

Re: Traffic Management Doesn't seem to be working

Post by bunger »

Well, poop. I guess there's my answer.
edirschedl
Enthusiast
Posts: 44
Liked: 4 times
Joined: Jul 21, 2016 12:29 pm
Full Name: Emanuel Dirschedl
Contact:

[MERGED] Network Throttling for Backup Copy Jobs with DDBoos

Post by edirschedl »

Hello,

we run Backup Copy Jobs in our remote offices directly with DDBoost to our Data Domain repositories. Unfortunately we haven't found any possibility in VEEAM to do a Backup Copy Job with efficient DDBoost with activated Network Throttling until now. (We want to avoid WAN Accelerators, because we can't use DDBoost and we don't want to invest in capacity for the cache disk.)

With Backup Jobs there we can use the "Limit read and write data rates to" option for the repository. But with Backup Copy Jobs the limit will be ignored.
The other way with help of global network traffic rules works, but instead of limiting the network traffic, it limits the reading rate from the source repository. So we can't use the full effect of DDBoost and the reserved network traffic on the WAN line...


Do you have any other idea to throttle the network traffic over WAN?


Thank you,

Emanuel
PTide
Product Manager
Posts: 6408
Liked: 724 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Traffic Management Doesn't seem to be working

Post by PTide »

Hi,

Please make sure that the gateway which you've specified in DataDomain settings belongs to the scope of network throttling rules.

Thanks
foggy
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: [MERGED] Network Throttling for Backup Copy Jobs with DD

Post by foggy »

edirschedl wrote:With Backup Jobs there we can use the "Limit read and write data rates to" option for the repository. But with Backup Copy Jobs the limit will be ignored.
Could you please also elaborate on this one, since it doesn't look expected.
edirschedl
Enthusiast
Posts: 44
Liked: 4 times
Joined: Jul 21, 2016 12:29 pm
Full Name: Emanuel Dirschedl
Contact:

Re: [MERGED] Network Throttling for Backup Copy Jobs with DD

Post by edirschedl »

Currently we have a working throttling for the write direction (from branch office to us) with this method. We can also change it during a running backup copy job and we see a effect etc. So that makes no problems.
But the read direction (from us to the branch office) won't be limit by the "Limit read and write data rates to" option. And we saw, that: If a new backup copy cycle starts, first there is a lot of reading from our Data Domain and without limiting the traffic is too high for the WAN line - which isn't acceptable during business hours.

So I don't understand the behaviour of this option or it seems that it doesn't work right in our environment.
foggy
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Traffic Management Doesn't seem to be working

Post by foggy »

Actually traffic throttling rules should also work in the opposite direction, since they are bi-directional. As for the read/write rate limit, I'm also not sure why it does not have effect if set correctly for the source repository, so recommend contacting support for a closer look at your setup.
Andreas Neufert
VP, Product Management
Posts: 6707
Liked: 1401 times
Joined: May 04, 2011 8:36 am
Full Name: Andreas Neufert
Location: Germany
Contact:

Re: Traffic Management Doesn't seem to be working

Post by Andreas Neufert » 1 person likes this post

From customer feedback:

BCJ and BCJ with WAN Acceleration work with Traffic Rules.
Traffic Rules need to be set in both directions (specifically with WAN Acceleration as some traffic flow in the opposite direction).

DDBoost/Catalyst and CIFS Traffic is not limited by traffic rules.

DDBoost/Catalyst Traffic is not limited by the Repository throughput setting.
Post Reply

Who is online

Users browsing this forum: Bing [Bot], Brian.Knoblauch, Google [Bot], Semrush [Bot] and 294 guests