BACK TO KB LIST

Throttling Rules Not Being Applied

KB ID:	1924
Product:	Veeam Backup & Replication \| 10 \| 11 \| 12 \| 12.1
Published:	2014-09-05
Last Modified:	2022-04-14

By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

Oops! Something went wrong.

Please try again later.

Challenge

A configured Network Throttling rule does not appear to be taking effect.

Solution

Traffic can only be throttled between backup infrastructure components where the Veeam Data Movers are deployed. These components differ depending on a data protection scenario. For more information, review the table within the Veeam Backup & Replication User Guide.
Traffic throttling does not apply to restore tasks.

More Information

References

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

Product

Topic

Description

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Verify your email to continue your product download

We've sent a verification code to:

An email with a verification code was just sent to

Didn't receive the code? Click to resend in sec

Didn't receive the code? Click to resend

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.