Hi Zoltan, Is the long-running backup working on system state? I haven't found a direct cause --> effect relationship to client APAR IC63094, but take a look at that APAR and see if, after applying the fix, the problem you are seeing goes away.
I should mention to all: IC63094 describes a problem with long-running system state backups. This APAR may be of interest to you. Best regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/i...@ibmus Internet e-mail: [email protected] IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <[email protected]> wrote on 2010-03-05 16:26:01: > [image removed] > > Long running backup pinning log > > Zoltan Forray/AC/VCU > > to: > > ADSM-L > > 2010-03-05 16:26 > > Sent by: > > "ADSM: Dist Stor Manager" <[email protected]> > > Please respond to "ADSM: Dist Stor Manager" > > I recently started having issues with my log going over 80% (5.5.3). Doing > a "show logpinned" usually points to a long (18-hours) running backup > session for one particular node. > > This is starting to happen more and more frequently. > > Once I kill the session, the log utilization drops to almost nothing since > there has been a DB backup run earlier in the day. > > Any suggestions on how to handle this besides killing the session? The > node is a standard 2K3 box using the 6.1.2.0 client. It is just a very > slow/busy box. The long backups (times vary from 11-19 hours) often dump > 120GB of data. > Zoltan Forray > TSM Software & Hardware Administrator > Virginia Commonwealth University > UCC/Office of Technology Services > [email protected] - 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
