https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxOTI0IiwiaGFzaCI6IjE0Y2M2MzZjLWJlZDctNDdkOS1hYmY1LWM4YzUyZjJkOTk1NiJ9
1-800-691-1991 | 9am - 8pm ET
EN

Throttling Rules Not Being Applied

Challenge

When creating rules for traffic throttling, the rules don’t take effect and jobs run at normal processing speeds.

Cause

One or more of the servers on which Veeam agents are running (repository server, Hyper-V host(s)/offhost proxy, VMware backup proxy) have more than one NIC.

Solution

Throttling rules must be created for all NICs for the machines on which Veeam Agents will run.  When a job runs, a port for the veeamagent.exe process is opened on each NIC of the source and target servers, even if that NIC is not responsible for source agent to target agent data transfer.  Below is an example of how the rules would need to be applied.
 
Source VMware backup proxy or Hyper-V host/Offhost proxy IPs:  (2 NICs) 10.0.0.30, 192.168.1.35
Target repository/proxy server or target Hyper-V host (in the case of Hyper-V replication) IPs: (2 NICs) 10.0.0.31, 192.168.1.26

User-added image

KB ID:
1924
Product:
Veeam Backup & Replication
Version:
7.x
Published:
2014-09-05
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later