About configuring 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:
The bandwidthlimit parameter in the
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.
The bandwidthlimit parameter applies to NetBackup 220.127.116.11 and later.
By default, bandwidthlimit=0.
The agent.cfg file resides in the following directory:
The OPTDUP_BANDWIDTH parameter in the
file specifies the per job bandwidth.
OPTDUP_BANDWIDTH applies only if the bandwidthlimit parameter in the
file is zero.
If OPTDUP_BANDWIDTH and bandwidthlimit are both 0, bandwidth per replication job is not limited.
By default, OPTDUP_BANDWIDTH = 0.
See About the pd.conf configuration file for NetBackup deduplication.
See Editing the pd.conf deduplication file
See pd.conf file settings for NetBackup deduplication
See About MSDP optimized duplication within the same domain
See Optimized MSDP duplication within the same domain requirements
See Optimized MSDP duplication within the same domain limitations
See Configuring MSDP optimized duplication copy behavior
See Configuring optimized duplication of deduplicated data