Network Throttling for Aux Copies

Hi @Abdul Wajid - I’d agree that throttling at the source will give you more flexibility. I am assuming it's the remote sites that need to throttle their outbound more than the destination media agent(s) need to throttle inbound traffic.

Just in case - make sure that you don't have 8400 (CVD port) as an ‘additional port’ on the network settings and it would bypass throttling. Sometimes that was done to improve performance a few years ago.

Hi @Damian Andre  - Thank you. We don't have that advanced setting. We have two media agents at the destination. Should we select both in the client selection list? If we select both, the throttling is applied on both or both get half of what we set? When this setting is changed, it reflects on the running jobs or on the next scheduled jobs? I was thinking of a way to monitor the network performance using a script and change the throttling values when the link is over-utilized on the go.

Hello @Abdul Wajid, their are a few different ways to go about this.

1. If all your Aux copies are going to one site with 2 Media Agents, and these 2 destination Media Agents only handle Aux Copies and not local backups then you can just setup throttling for Send on the source MediaAgents and Receive on the destination MediaAgents, obviously setting up different times with Client Throttling. You will also want to do Absolute throttling and set it for the amount of bandwidth you want to send and receive (do not cut in half or split between source and destination) 
2. If the Destination MediaAgents (for the aux copy) do also local backups then you will want to forgo the Receive options on the destination MA.
3. Also if you have both local and aux copies going to this destination MA and you only want to throttle the Aux copies then there is an option to use Copy throttling which I will list the documentation below, you can set throttling per copy. Setting Network Bandwidth Throttling for a Storage Policy Copy (commvault.com)

If you do Client Throttling then it will happen on running jobs unless you select the option “Exclude Immediate Jobs”, when doing Copy throttling it will be the next scheduled or manually ran jobs after the changes have been made.

Hope this answers your questions and concerns.

Thank You

@Joey Gorana Thank you for the response. We have two destination media agents which are also responsible for backups at local site. 

We are configuring the throttling on the source media agent and we are controlling the send traffic. We have multiple rules in the throttling configuration, these rule apply only to the jobs that get triggered in that specific window, that job keeps on running following the same rule under which it was triggered and it does not adjust the send rate when the new schedule kicks in. For example, if a job started at 12:15PM, it starts using 100Mbps and does not adjusts down to 25Mbps when the second schedule comes into play. 

Rules:

12:01PM -- 6PM --- 100Mbps
6PM ---- 11:59PM --- 200MBps

I could not find the option “Exclude Immediate Jobs” in the throttling configuration. Maybe I am not doing it the right way.

We cannot use the copy configuration because that sets a static limit. We want to control the send traffic dynamically. What would be the best way to approach this?