How much bandwidth will/does NetWorker use?

This Wiki is brought to you by Backup Central, where you can find the Mr. Backup Blog, Forums, and a mailing list for each forum!
Backup FAQs	Service Providers	Backup Software	Backup Hardware	Backup Book Wiki	Free Stuff	Miscellaneous

A. Bruno Voigt posted (27 Dec 1999): These are the hints I got: "Joseph Ortiz" <jortiz@vangard.com>

By its very nature, backup software is designed to maximize throughput in order to back up as much data in as short as time as possible. Consequently there are NO provisions to tune the amount of bandwidth a given backup product uses (at least not in Legato or Veritas land) when its backing up clients. In most cases, the backup engine (on enterprise size backup environments at least) has access to a separate segment dedicate to the backup jobs so as not to interfere with regular LAN traffic. The only thing YOU can do here is control the number of parallel data streams the client generates and the time the backups occur. If you want that type of bandwidth control, you need to look at REPLICATION products like Double Take from NSI Software that let you do that type of tuning and that also can be configured to work in conjunction with products like Networker. You're only other option would be looking into the possibility of a serverless backup SAN using something like the Legato Celestra product. Wayne Chan <Wayne.Chan@EBay.Sun.COM>

You can reduce the client parallellism of the IP-WAN client from Networker's client setup page. While the default is 4 but you can reduce this number to fit your needs. It does not directly limit the network bandwidth but it reduces the overall client-to-server traffic/activities in turns it reduces the network traffic accordingly. "Heiss, Georg (Z-EDV)" <Georg.Heiss@KVB.de>:

You can try this: (ip-addresse from networker-server)

 access-list 10 permit 239.1.1.1 0.0.0.0
 priority-list 1 protocol ip low list 10

The last hint refers to configure the ip router handling the WAN connection so that it gives the ip traffic from the backup server a lower prio than the other traffic. The above example is for a cisco 36[24]0 router, it gives the ip packets FROM the backup-server a lower priority. Thats not yet what I want because the clients are the machines sending the bulk backup-traffic and the backup-server sends only some ACKs etc?! But the above config seems to help by slowing down the backup ip sessions not to disturb the production ip traffic from the client machines during a backup session. I am still searching for a better way to specify a dedicated bandwith eg. 100KB/s in the cisco router for traffic coming from the networker ip ports.. VERITAS NetBackup *DOES* allow per-subnet and even per-client bandwidth throttling, if there is a concern about monopolizing the wire with backup traffic.