Most of our problems like this are SQL db backups that are one big file.
We ask the Win admins and DBA's to change the backup such that it gets
written in a bunch of smaller pieces.

Try and identify the big file that is is being backed up.  Can it be
broken into smaller pieces?  Can it be zip'ed into a smaller file?  Can
the node be moved to a different TSM instance that doesn't have as much
activity.  Does the file even need to be backed up?

Rick







From:   Zoltan Forray <zforray AT VCU DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
Date:   04/16/2013 09:37 AM
Subject:        Re: Addressing "log pinned" condition on V6 server
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



But, how do you address/resolve this kind of problem?

On Tue, Apr 16, 2013 at 9:22 AM, Allen S. Rout <asr AT ufl DOT edu> wrote:

> On 04/16/2013 08:59 AM, Zoltan Forray wrote:
> >
> > The active session is only up to 222GB so it isn't volume - just one
long
> > transaction, I guess?
>
> (reliatively) Big files, transmitted (relatively) slowly, are my most
> common log-pin culprit.
>
> - Allen S. Rout
>



--
*Zoltan Forray*
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html




-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.