Did you examine the TSM Server activity log closely? Was there a problem where a tape did not get mounted in time? How many "stripes" are you using for the backup? If you are using multiple stripes and one of those stripes is waiting for the TSM server to mount a tape, it can cause this. I have seen this when the TSM Server does not have enough available tapes mounted to satisfy the DP/SQL request. The "Waiting on TSM server...." indicates that DP/SQL is waiting for some event on the TSM Server to occur before it can continue sending any more data. Is it possible that some TSM Server event pre-empted the DP/SQL backup and took one of the tapes that was needed to satisfy a multiple stripe DP/SQL backup request?
You should start on the TSM Server... in the activity log to find out what it thinks happened. Thanks, Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 12/14/2007 09:52:59 AM: > I have a dba that has one sql server that has "tsm hang" issues > according to him. They have a full backup job that backs up 7 sql db's. > The size is about 80GB total. Sometime it backs them all up with no > issues, sometime it says "waiting on tsm server" but if I look at "q se" > there are no active sessions. Right now there is one running from last > night and it has only backed up 12.5GB in 9 hours. below are some client > details and log details. Anyone have any ideas. Other sql backups run > just fine along with the other 15TB that backup each night, but of > course DBA's say it's a TSM issue. > Here is what they see when it hangs: > > Full: 3 Read: 658505728 Written: 655360000 Rate: 480.95 Kb/Sec > Full: 3 Read: 658505728 Written: 655360000 Rate: 480.59 Kb/Sec > Full: 3 Read: 658505728 Written: 655360000 Rate: 480.23 Kb/Sec > Full: 3 Read: 658505728 Written: 655360000 Rate: 479.87 Kb/Sec > > Waiting for TSM > server.................................................................. > ...................... > > clint info: > > Node Name: WHQWPSQLCL1RS01_SQL > Platform: TDP MSSQL Win32 > Client OS Level: 5.02 > Client Version: Version 5, Release 3, Level 3.0 > Policy Domain Name: SQL > Last Access Date/Time: 12/14/07 08:00:05 > Days Since Last Access: <1 > > > thanks, > Rod
