Turn compression off and see what happens.  Client compression is not
advisable with fast networks.

What does your client CPU utilization look like?

_____________________________
William Mansfield
Senior Consultant
Solution Technology, Inc
630 357 7744 x338



                    Rob Schroeder
                    <robs@FAMOUSFOO        To:     ADSM-L AT VM.MARIST DOT EDU
                    TWEAR.COM>             cc:
                    Sent by: "ADSM:        Subject:     performance question
                    Dist Stor
                    Manager"
                    <ADSM-L AT VM DOT MARI
                    ST.EDU>


                    09/28/2001
                    02:33 PM
                    Please respond
                    to "ADSM: Dist
                    Stor Manager"






I am running TSM client 3.7.2 on a Win2000 server with Service pack 2.  The
TSM server is Win2000 SP2 and using TSM 4.1.3.  I realize I need to upgrade
the client, but I that will not happen until next week.  My dilemma is
this: the server backs up to the TSM server directly to a DISK pool that is
quite large, the network is Gigabit, and this client is the only client
that is talking to the server.  There are no other applications running on
either server.  I would expect this baby to scream, but instead it is
dogging.  I am getting just 2 MB/sec throughput and would expect to be
pushing the network.  Here is the options file I am using:

LANG AMENG
tcpserveraddress fftsm01
changingretries 0
resourceutilization 10
schedlogretention 10
errorlogretention 10
compression yes
txnbytelimit 25600
largecommbuffers yes
tcpnodelay yes
compressalways no
tcpbuffsize 256
tcpwindowsize 50

Any ideas?

Rob Schroeder
Famous Footwear