Some things to try:
1. verify that the MTU is consistent for all nodes, from your cws:
[EMAIL PROTECTED]:/>dsh "netstat -i | grep css0"
unxa_sp: css0 65504 link#4 3496790 0 4212524 0 0
unxa_sp: css0 65504 192.168.17 unxa_sw 3496790 0 4212524 0 0
unxb_sp: css0 65504 link#4 3500733 0 3392237 0 0
unxb_sp: css0 65504 192.168.17 unxb_sw 3500733 0 3392237 0 0
unxc_sp: css0 65504 link#3 3435131 0 3620093 0 0
unxc_sp: css0 65504 192.168.17 unxc_sw 3435131 0 3620093 0 0
unxm_sp: css0 65504 link#5 3486660 0 5827317 0 0
unxm_sp: css0 65504 192.168.17 unxm_sw 3486660 0 5827317 0 0
unxp_sp: css0 65504 link#5 21731474 0 30705999 0 0
unxp_sp: css0 65504 192.168.17 unxp_sw 21731474 0 30705999 0 0
unxr_sp: css0 65504 link#6 82760978 0 79211973 0 0
unxr_sp: css0 65504 192.168.17 unxr_sw 82760978 0 79211973 0 0
Yours should be: 65520.
2. my dsmserv.opt
TCPWINDOWSIZE 2048
BUFPoolsize 262144
3. client dsm.sys settings:
unxr:/usr/tivoli/tsm/client/ba/bin>cat dsm.sys
Servername unxr
NODENAME unxr
TCPPort 1500
SHMPort 1510
TCPServeraddress 127.0.0.1
tcpb 64
tcpwindowsize 2048
tcpnodelay Yes
TXNbytelimit 2097152
resourceutilization 10
passwordaccess generate
LARGECOMMBUFFERS No
4. are you sure you want client compression?
5. And again, try and identify the bottleneck.
Miles
>>> "Muthyam Reddy" <[EMAIL PROTECTED]> 11-Sep-03 10:13:50 AM >>>
** High Priority **
thanks a lot for quick responce.
we have
AIX:4.3.3.0
PSSP version:3.1.1.0
OS kernel:64bit in all SP nodes
TSM Tapedrives:IBM 3590 Tape Drive and Medium Changer.
I have set css0 spoolsize,rpoolsize to 16777216 in both client and server.
TSM server type:S80, 7017
SP switch css0 type:SP Switch Communications Adapter (Type 6-F)
TSM software level:5.1.5.0 in both client and server.
all out nodes are hoocked to SHARK disk storage.those SSA drives.
dsm.sys parametrs at client.
tcpnodelay yes
compression yes
LARGECOMMBUFFERS NO
TCPwindow 2048
TCPbuffsize 256
TCPNodelay yes
PASSWORDACCESS generate
resourceutilization 8
thanks and regards
muthyam
>>> "Miles Purdy" <[EMAIL PROTECTED]> 09/10/03 03:47PM >>>
That seems terribly slow. 430 GB in 14 hours is only 8.7 MB/s aggregate throughput.
Over four streams that's only 2 MB/s/stream. It has been my experience that the source
hdisks are usually the bottleneck.
There are only two tunables for the switch adapter, rpoolsize and spoolsize.
These can be changed, for example:
chdev -l css0 -a spoolsize=14680064
chdev -l css0 -a rpoolsize=16777216
A couple of things that come to mind:
- are you mixing machines with 32 and 64 bit kernels on the same SP Switch?
- what version of AIX are you running? What version of PSSP? What tape drives do you
have?
- what are your vmtune settings?
- where is the bottleneck?
- is the switch performing well?
- check the source disks
- check the VMM
>>> [EMAIL PROTECTED] 10-Sep-03 2:18:05 PM >>>
** High Priority **
Hi TSMers,
I hope someone got experiance on same before .
This is problem about db2(7.1) backups on high speed switch to TSM .Present we are
taking 430Gb of data to tsm which is taking 14 hrs to finish.recently I have changed
couple of paramters on 'css' and 'no' to improve performance based on IBM docs.Still
my backups takes same time.
no doubt I missed some parts on TSM/AIX/db2 to lubricate.
Please can any one dump some ideas to fix this this and how long its taking in ur
environment same setup.
We are using four session on db2(7.1) and copying to tape pools directly.
please send ur back times with same environments.
please send me some tips to make my backups fast.
please write if wants information.
thanks and regards
muthyam
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
This electronic mail transmission contains information from Joy Mining Machinery
which is confidential, and is intended only for the use of the proper addressee.
If you are not the intended recipient, please notify us immediately at the return
address on this transmission, or by telephone at (724) 779-4500, and delete
this message and any attachments from your system. Unauthorized use, copying,
disclosing, distributing, or taking any action in reliance on the contents of
this transmission is strictly prohibited and may be unlawful.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
<<privacy>>
