Paul -

Certainly, "de-tuning" the TSM backups will reduce the impact, where
the most obvious tactic is to minimize RESOURceutilization. And you
can get more drastic via MEMORYEFficientbackup Yes. Depending upon
the file population, the influx of the Active files list at the
beginning of an incremental will always have a "fixed" impact. Beyond
that, you can deprioritize the TSM client process at the OS level.

If you want to get silly, turn on client tracing: *that* will reduce
throughput, for sure.

   Richard Sims

On Apr 25, 2006, at 2:13 PM, Paul Zarnowski wrote:

We have a small number of users here who are complaining that when a
TSM backup runs on their client system, it monopolizes use of their
network card.  They are looking for a way to throttle back TSM's use
of the network.  Has anyone else run into this?  Any ideas?  The only
thing I've come up with is to configure a secondary NIC at 10MB/s and
point these users at that card.  This seems crude to me, so other
ideas would be welcome.