There is a way to do that.   Just set the backup process to "BelowNormal"  or 
"Low" priority.



Troy Frank
Network Services
University of Wisconsin Medical Foundation
608.829.5384

>>> rbs AT BU DOT EDU 4/26/2005 10:15:24 AM >>>
Paul -

In Unix, at least, a less important process (the backup, in this case)
can be "reniced" to reduce its impact, giving the more important
processes a higher relative priority in accessing resources. There may
be a similar mechanism for Windows.

Incremental backups have a considerable impact because of the Active
Files list they have to juggle. You could evaluate whether a
-INCRBYDate type backup would be viable for the involved systems, where
there is no list overhead.

Richard Sims

On Apr 26, 2005, at 10:52 AM, Paul Zarnowski wrote:

> At 07:33 PM 4/25/2005, Coats, Jack wrote:
>> Our solutions:
>> * Start backups when users have supposedly gone home.
>
> Thanks for the suggestions so far. I should have mentioned that this
> is
> for an application server who's performance is important 24x7. We do
> already schedule during off-peak, but even so the performance
> degradation
> caused by the TSM backup is noticed and is perceived as a problem.


Confidentiality Notice follows:

The information in this message (and the documents attached to it, if any)
is confidential and may be legally privileged. It is intended solely for
the addressee. Access to this message by anyone else is unauthorized. If
you are not the intended recipient, any disclosure, copying, distribution
or any action taken, or omitted to be taken in reliance on it is
prohibited and may be unlawful. If you have received this message in
error, please delete all electronic copies of this message (and the
documents attached to it, if any), destroy any hard copies you may have
created and notify me immediately by replying to this email. Thank you.