Tape change is not the issue. I was watching it for 5-10 minutes and it
was using the same tape. This was the first thing I checked. However, the
"waiting" messages keep appearing every so-many lines in the log.

I would have thought a 3590E1A on a SAN/FC connection would be fast enough
to keep up with this traffic, other than to rewind the tape.

Any way to improve this performance issue ?   Any server options I might
have missed  ?





Del Hoobler <hoobler AT US.IBM DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
08/20/2002 07:03 PM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: TDP for Domino Performance - redux


> Waiting for TSM server....
> Full: 3   Read: 152043520  Written: 148897792  Rate: 473.60 Kb/Sec
> Full: 3   Read: 152043520  Written: 148897792  Rate: 472.07 Kb/Sec
> Full: 3   Read: 152043520  Written: 148897792  Rate: 470.54 Kb/Sec
> Full: 3   Read: 152043520  Written: 148897792  Rate: 469.02 Kb/Sec
> Full: 3   Read: 152043520  Written: 148897792  Rate: 467.51 Kb/Sec
> Full: 3   Read: 152043520  Written: 148897792  Rate: 466.01 Kb/Sec
> Full: 3   Read: 152043520  Written: 148897792  Rate: 464.53 Kb/Sec
> Waiting for TSM server......
>
> We are wondering, why the "Waiting" messges ?   What is it waiting for ?

Zoltan,

These "waiting" messages are when the TSM API is waiting for the
TSM Server to respond to a "send data" verb. In other words,
TDP for Domino has sent a buffer full of data to the TSM Server
and the TSM Server is trying to find a spot for it.
If going directly to tape, it could be that the tape is positioning
or that a new tape is being mounted so more data can be stored.

Thanks,

Del

----------------------------------------------------

Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com

- Never cut what can be untied.
- Commit yourself to constant improvement.