Manual: 4.5 UNIX System Administrator's guide

Page: Pages 250 and 445

Modification Type: Addition

There are situations where a customer may need to limit the available bandwidth to NetBackup to ensure all data gets a chance to traverse the network. This can be useful in networks with firewalls that can be overrun by the amount of NetBackup data traffic.

If the customer needs to limit the amount of bandwidth used by NetBackup, so backups do not use all the available bandwidth, set the limits for both IP subnets and individual clients using the GUI in Master server | Host Properties | Bandwidth. (see page 250 for details in the 4.5 UNIX System Administrator's guide).

Or use the following entry in the master server's bp.conf file to reduce or limit the available bandwidth.

Example 1:
LIMIT_BANDWIDTH = 10.222.333.1 10.222.333.255 500  
This would limit the entire IP subnet 10.222.333.x to only 500 KB of bandwidth.

Example 2:
LIMIT_BANDWIDTH = 10.222.333.111 10.222.333.111 500
This would limit just the one client with the IP address 10.222.333.111 to only 500 KB of bandwidth.

Example 3:
LIMIT_BANDWIDTH = 10.222.333.1 10.222.333.255 500  
This would limit the entire IP subnet 10.222.333.x to only 500 KB of bandwidth.

LIMIT_BANDWIDTH = 10.222.333.111 10.222.333.111 0  
This would disable bandwidth limiting for just this one client with IP address 10.222.333.111.

Note: Setting the bandwidth higher for an individual client then it is for the range, NetBackup ignores that setting and uses the value for the range.

If the bandwidth limit for an individual client is equal to or lower than the value for the range, the client uses whichever value is the lowest.

Example 4:
LIMIT_BANDWIDTH = 10.222.333.1 10.222.333.255 500
LIMIT_BANDWIDTH = 10.222.333.111 10.222.333.111 300
In the above example, the client would use the lower value of 300 KB.

Note: This does not work with some types of backups (DB2, DataStore, Informix, Oracle, SQL-Backtrack, SQL-Server, Teradata etc.).