Thomas,
To get some immediate consider using the "randomize" setting on the TSM server 
combined with an extended backup window and limiting the number of machines 
that can backup concurrently with the "maxschedsessions" setting.

This will allow you to have some control over how many clients backup at one 
time.

For example; if you set your backup window for say 4 hours then tweak the 
randomize setting which will stagger your start times of the client backups by 
a set percentage. This keeps all of them from initiating their backups at once. 
Additionally, maxschedsessions will allow you to limit how many actual clients 
can connect at one time.

Obviously each environment is different and actual settings depend on variables 
such as total number of clients, amount of data, speed of network, etc, etc.

I suggest starting off conservatively, monitor the actlog for issues, and tweak 
as needed. I have used this approach many times for customers while campaigning 
for increased bandwidth resources.

Rick Adamson

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Tom Taylor
Sent: Wednesday, May 14, 2014 10:56 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Bandwidth

Good morning,

        I run TSM 6.3.4


How do I throttle bandwidth so that the clients don't choke the network during 
backups. I have already set a large window for the clients to use, and I am 
reading about client side de-duplication, and adaptive file backup. Are these 
the only two avenues to reduce the bandwidth used by TSM?








Thomas Taylor
System Administrator
Jos. A. Bank Clothiers
Cell (443)-974-5768