The communication between client and server is two-way. For example, a
large RECVDBYTES on one session would be indicative of the existing backup
info the server returns to the client (probably a producer session), while
the smaller RECVDBYTES on the other session (the consumer session) would
be indicative of "end-transaction" and "confirm" processing that goes on
between the client and server during the backup.

This would be normal.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




"Dearman, Richard" <rdearm1 AT UIC DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
11/12/2001 16:57
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        confused



Why is it every time I backup a server my q sess output at my tsm server
shows my send bytes going up as well as my recvdbytes.  I'm not doing a
restore to the node so shouldn't only my recvdbytes statistics go up.
125,581 Tcp/Ip IdleW 2 S 81.0 M 1.9 K Node WinNT UICMC20
125,803 Tcp/Ip IdleW 16 S 1.3 K 307.4 M Node WinNT UICMC20

***************************EMAIL  DISCLAIMER**************************
This e-mail and any files transmitted with it may be confidential and are
intended solely for the use of the individual or entity to whom they are
addressed.   If you are not the intended recipient or the individual
responsible for delivering the e-mail to the intended recipient, any
disclosure, copying, distribution or any action taken or omitted to be
taken
in reliance on it, is strictly prohibited.  If you have received this
e-mail
in error, please delete it and notify the sender or contact Health
Information  Management (312) 996-3941.