Generally, a replication throttle is seen as a limiting factor in the overall speed of replication, but set correctly, a replication throttle can enhance a replication configuration.
The reason for this is because after 5 mbps the Data Domain assumes unlimited bandwidth. In large environments, when the Data Domain is able to hit the upper limit for transfer rate between sites, this can cause issues over time.
By setting a replication throttle, it is possible to inform the Data Domain what that bandwidth limit is, so it can gracefully adjust for this limitation rather than dropping streams that would cause the Data Domain to exceed this limit.
In practice, it is best to set the Data Domain replication throttle to 90-95% of the desired maximum bandwidth so that the Data Domain is not in danger of overutilizing the replication network resulting in dropped streams.
To check for a replication throttle, use the following command:
replication throttle show
Throttle: Default
Time Sun Mon Tue Wed Thu Fri Sat
---- --- --- --- --- --- --- ---
07:00 - unlimited - - - - -
---- --- --- --- --- --- --- ---
All units in bps (bits per second).
Active schedule: Mon, 07:00 at unlimited bps.
Actual throttle value: unlimited bps
To add a replication throttle, use the following command:
replication throttle add <day> <time> <throttle rate in bps or KB>
Example:
replication throttle add mon 0700 1000Kbps
..."Kbps" units specified; 1000 * 1000 = 1000000 bps (1000 Kbps).
> Changing schedule for Mon at 07:00 to 1000K bps (was unlimited bps)
Verify that the changes are in place:
replication throttle show
Throttle: Default
Time Sun Mon Tue Wed Thu Fri Sat
---- --- --- --- --- --- --- ---
07:00 - 1000K - - - - -
---- --- --- --- --- --- --- ---
All units in bps (bits per second).
Active schedule: Mon, 07:00 at 1000K bps.
Actual throttle value: 1000K bps
For additional information about how to configure replication throttle on the Data Domain see
Data Domain - Replication Throttle.
Note replication throttle is a global setting on the Data Domain. As such it affects Avamar controlled MFR replication as well as Data Domain native replications.