I agree on the speed/duplex. I have personally seen speed/duplex
mismatch cause this. I don't personally have issues with Auto, just
make sure both sides(server and switch) match.
Jeremy Curtis
Backup Administrator / Network Technician
Vail Resorts, Inc.
(970) 845-1921
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Kelly Lipp
Sent: Thursday, March 22, 2007 3:56 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Wiindows 2000 and 2003 servers backups very poor
performance
I will amplify Curtis' call on this: check the NICs. Especially if you
are on 100MB Ethernet. For GigE, you generally can't choose, but make
it all the same in the path between the server and TSM.
As for testing: try an ftp of a large file (a gig or so so it stays on
the wire for a minute or so). If this is faster than you are getting
from TSM, you have a TSM problem. If it is the same speed, you have a
network problem.
Kelly J. Lipp
VP Manufacturing & CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777
[EMAIL PROTECTED]
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Carpenter, Curtis
Sent: Thursday, March 22, 2007 3:52 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Wiindows 2000 and 2003 servers backups very poor
performance
I would make sure whatever speed and duplex setting you have the nic set
to, you should set the switch port to match. I would try to avoid
setting both to autonegotiate, as I have personally seen horrible
performance with that setting. Also, run diags on network interfaces to
rule out any hardware problems. Are u using a seperate nic for your
tivoli backups or are u using just one nic for all network communication
on these servers?
--Original Message--
From: Timothy Hughes
To: ADSM-L
ReplyTo: ADSM-L
Sent: Mar 22, 2007 3:33 PM
Subject: [ADSM-L] Wiindows 2000 and 2003 servers backups very poor
performance
Hello,
We have about 5 or 6 Windows Servers whose backups performance is very
very poor these backups start a midnight and run throughout the whole
day and sometimes run for a couple days I have been reading different
options including the DISKBuffsize option, I know poor networking
performance can be caused by a number of factors and not sure which
parameter to look at first.
Here is an example of one of the clients dsm.opt file, They all
basically look the same and the parameters matches TSM windows clients
recommendations.
Lang Ameng
Domain ALL-LOCAL
TCPSERVERADDRESS .xxx.x.xx.xx
Passwordaccess generate
TCPCLIENTADDRESS xx.xx.xxx.xx
NODENAME
SUBDIR YES
REPLACE PROMPT
TCPB 32
TCPW 63
SCHEDMODE PROMPTED
TXNBYTELIMIT 25600
ERRORLOGNAME
SCHEDLOGNAME
ERRORLOGRETENTION 14
SCHEDLOGRETENTION 7
TCPNODELAY YES
RESOURCEUTILIZATION 3
LARGECOMMBUFFERS YES
CHANGINGRETRIES 2
COMPRESSION
BACKUPREG YES
MANAGEDSERVICES WEBCLIENT SCHEDULE
Windows 2000 and 2003 servers
TSM server 5.3.4
TSM client 5.3.4
