|
Re: Backup Performance
2005-06-26 16:04:12
I changed resourcesutilization from 5 back to 3, then backup
performance is still very good. I guess the root cause is the
tcpwindowsize that HP-UX does not support 128. Thanks for everyone's
help!!!
06/25/05 22:40:13 --- SCHEDULEREC STATUS BEGIN
06/25/05 22:40:13 Total number of objects inspected: 376,929
06/25/05 22:40:13 Total number of objects backed up: 897
06/25/05 22:40:13 Total number of objects updated: 0
06/25/05 22:40:13 Total number of objects rebound: 0
06/25/05 22:40:13 Total number of objects deleted: 0
06/25/05 22:40:13 Total number of objects expired: 58
06/25/05 22:40:13 Total number of objects failed: 0
06/25/05 22:40:13 Total number of bytes transferred: 181.80 GB
06/25/05 22:40:13 LanFree data bytes: 181.80 GB
06/25/05 22:40:13 Data transfer time: 1,150.47 sec
06/25/05 22:40:13 Network data transfer rate: 165,701.22 KB/sec
06/25/05 22:40:13 Aggregate data transfer rate: 17,931.77 KB/sec
06/25/05 22:40:13 Objects compressed by: 0%
06/25/05 22:40:13 Elapsed processing time: 02:57:11
06/25/05 22:40:13 --- SCHEDULEREC STATUS END
06/25/05 22:40:13 --- SCHEDULEREC OBJECT END 06/25/05 19:45:00
On 6/24/05, Sung Y Lee <sunglee AT us.ibm DOT com> wrote:
>
>
> Np.. Glad you were able to resolve the issue.
> Now that's pretty good backup speed.
>
> Sung Y. Lee
> William <weiduo.deng AT gmail DOT com>
>
>
>
>
> William <weiduo.deng AT gmail DOT com>
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> 06/23/2005 10:19 PM
> Please respond to
> William <weiduo.deng AT gmail DOT com>
>
> To
> ADSM-L AT VM.MARIST DOT EDU
> ADSM-L AT VM.MARIST DOT EDU
>
> cc
>
> Subject
> Re: Backup Performance
>
> Thanks Sung. I did not find any lanfree related issue. As I mentioned
> in previous post. I changed 2 parameters:
> 1. resouceutilization from current 3 to 5
> 2. tcpwindowsize from current 128 to 63
>
> Now the backup looks very good.
>
> 06/23/05 20:26:13 --- SCHEDULEREC STATUS BEGIN
> 06/23/05 20:26:13 Total number of objects inspected: 376,443
> 06/23/05 20:26:13 Total number of objects backed up: 749
> 06/23/05 20:26:13 Total number of objects updated: 0
> 06/23/05 20:26:13 Total number of objects rebound: 0
> 06/23/05 20:26:13 Total number of objects deleted: 0
> 06/23/05 20:26:13 Total number of objects expired: 473
> 06/23/05 20:26:13 Total number of objects failed: 0
> 06/23/05 20:26:13 Total number of bytes transferred: 58.45 GB
> 06/23/05 20:26:13 LanFree data bytes: 54.56 GB
> 06/23/05 20:26:13 Data transfer time: 317.63 sec
> 06/23/05 20:26:13 Network data transfer rate: 192,974.37 KB/sec
> 06/23/05 20:26:13 Aggregate data transfer rate: 23,679.02 KB/sec
> 06/23/05 20:26:13 Objects compressed by: 0%
> 06/23/05 20:26:13 Elapsed processing time: 00:43:08
>
>
> On 6/23/05, Sung Y Lee <sunglee AT us.ibm DOT com> wrote:
> > Looking at the config, this appears to be lanfree backup client. If the
> > lanfree is broken, then normally TSM client will default to tcpip over
> lan.
> > If this is so, then I do see TSM storage agent version mismatch. From
> what
> > I understand, TSM server code and TSM storage agent should match.
> > Is it possible that Lanfree was put in place to over come possible network
> > performance issue?
> >
> > Check the activity log for q actlog begind=-1 s=lanfree. If you are not
> > getting any lanfree for this client or any other clients then I would
> > examine the SAN/Switch configuration. Sometimes I have seen where recycle
> > of storage agent can help with this.
> >
> > Thanks,
> >
> > Sung Y. Lee
> >
> > "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 06/23/2005
> > 02:54:38 PM:
> >
> > > I have a performance issue here, any input would be greatly appreciated.
> > >
> > > TSM Server: 5.3 on AIX 5.3
> > > TSM Client: 5.2.3 on HP-UX B.11.11
> > > TSM Storag Agent 5.2.3
> > > Tape Library: IBM 3584 LTO2 with 12 drives
> > >
> > > The backup throughput is not good.
> > >
> > > 06/17/05 06:59:51 Total number of objects inspected: 375,305
> > > 06/17/05 06:59:51 Total number of bytes transferred: 137.57 GB
> > > 06/17/05 06:59:51 Elapsed processing time: 11:16:41
> > > 06/18/05 05:15:41 Total number of objects inspected: 375,766
> > > 06/18/05 05:15:41 Total number of bytes transferred: 120.24 GB
> > > 06/18/05 05:15:41 Elapsed processing time: 09:32:08
> > > 06/19/05 06:37:26 Total number of objects inspected: 375,840
> > > 06/19/05 06:37:26 Total number of bytes transferred: 142.51 GB
> > > 06/19/05 06:37:26 Elapsed processing time: 10:54:18
> > > 06/20/05 06:04:59 Total number of objects inspected: 375,881
> > > 06/20/05 06:04:59 Total number of bytes transferred: 122.82 GB
> > > 06/20/05 06:04:59 Elapsed processing time: 10:21:51
> > > 06/21/05 04:58:34 Total number of objects inspected: 376,030
> > > 06/21/05 04:58:34 Total number of bytes transferred: 123.83 GB
> > > 06/21/05 04:58:34 Elapsed processing time: 09:15:27
> > > 06/22/05 06:44:12 Total number of objects inspected: 376,119
> > > 06/22/05 06:44:12 Total number of bytes transferred: 138.77 GB
> > > 06/22/05 06:44:12 Elapsed processing time: 11:01:06
> > > 06/23/05 13:45:24 Total number of objects inspected: 376,478
> > > 06/23/05 13:45:24 Total number of bytes transferred: 291.25 GB
> > > 06/23/05 13:45:24 Elapsed processing time: 18:02:19
> > >
> > >
> > > dsm.sys
> > > SErvername tsm
> > > COMMmethod TCPip
> > > TCPPort 1500
> > > HTTPport 1581
> > > WEBPORTS 1582 1583
> > > TCPServeraddress 10.12.1.20
> > >
> > > node sm54
> > >
> > > passwordaccess generate
> > > Schedmode prompted
> > >
> > > errorlogname /opt/tivoli/tsm/client/ba/bin/dsmerror.log
> > > errorlogretention 30
> > >
> > > schedlogname /opt/tivoli/tsm/client/ba/bin/dsmsched.log
> > > schedlogretention 7
> > >
> > > resourceutilization 3
> > > tcpwindowsize 128
> > > tcpbuffsize 64
> > > TCPNodelay Yes
> > >
> > > largecommbuffers no
> > > compression no
> > >
> > > enablelanfree yes
> > > LANFREECommmethod TCPIP
> > > LANFREETCPPort 1500
> > > TxnByteLimit 2097152
> > >
> > > Except I found one warning message from dsmerror.log, nothing else:
> > > 06/17/05 19:43:32 SetSocketOptions(): Warning. The TCP window size
> > > defined to ADSM is not supported by your system.
> > > It will be to set default size - 65535
> > > 06/18/05 19:43:07 SetSocketOptions(): Warning. The TCP window size
> > > defined to ADSM is not supported by your system.
> > > It will be to set default size - 65535
> > > 06/19/05 19:43:07 SetSocketOptions(): Warning. The TCP window size
> > > defined to ADSM is not supported by your system.
> > > It will be to set default size - 65535
> > > 06/20/05 19:43:06 SetSocketOptions(): Warning. The TCP window size
> > > defined to ADSM is not supported by your system.
> > > It will be to set default size - 65535
> > > 06/21/05 19:43:05 SetSocketOptions(): Warning. The TCP window size
> > > defined to ADSM is not supported by your system.
> > > It will be to set default size - 65535
> > > 06/22/05 19:43:04 SetSocketOptions(): Warning. The TCP window size
> > > defined to ADSM is not supported by your system.
> > > It will be to set default size - 65535
>
>
>
>
>
|
|
|
