Correct.
As per reference to page 119 in my previous post, herewith extract:
About configuring MSDP optimized duplication and replication bandwidth
Each optimized duplication or Auto Image Replication job is a separate process or
stream. The number of duplication or replication jobs that run concurrently
determines the number of jobs that contend for bandwidth. You can control how
much network bandwidth that optimized duplication and Auto Image Replication
jobs consume.
Two different configuration file settings control the bandwidth that is used, as follows:
bandwidthlimit
The bandwidthlimit parameter in the agent.cfg file is the global bandwidth setting. You can use this parameter to limit the bandwidth that all replication jobs use. It applies to jobs in which a
Media Server Deduplication Pool is the source. Therefore, configure it on the source storage server.
If bandwidthlimit is greater than zero, all of the jobs share the bandwidth. That is, the bandwidth for each job is the bandwidthlimit divided by the number of jobs.
If bandwidthlimit=0, total bandwidth is not limited. However, you can limit the bandwidth that each job uses. See the following OPTDUP_BANDWIDTH description.
If you specify bandwidth limits, optimized duplication and replication traffic to any destination is limited.
By default, bandwidthlimit=0.
The agent.cfg file resides in the following directory:
■ UNIX: storage_path/etc/puredisk
■ Windows: storage_path\etc\puredisk
OPTDUP_BANDWIDTH
The OPTDUP_BANDWIDTH parameter in the pd.conf file specifies the per job bandwidth.
OPTDUP_BANDWIDTH applies only if the bandwidthlimit parameter in the agent.cfg file is zero.
If OPTDUP_BANDWIDTH and bandwidthlimit are both 0, bandwidth per replication job is not limited.
By default, OPTDUP_BANDWIDTH = 0.
