Check the TCPWINDOWSIZE setting on the client side. If you're using
something larger than the default (which happens to be 63), this can
actually be counterproductive, as the network may eventually start to
shrink the window. I've seen users try to set a larger value than the
default, and get bit by this.
Also, are other similarly sized clients are experiencing the same problem
(size being number of files, not size)?
Check if any heavy-duty TSM server housekeeping is going on, such as
inventory expiration.
Best regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com
IBM Tivoli Storage Manager support web page:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 2010-09-09
18:57:16:
> From: "Prather, Wanda" <wPrather AT ICFI DOT COM>
> To: ADSM-L AT vm.marist DOT edu
> Date: 2010-09-09 19:04
> Subject: Re: long time for client backup
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>
> Do a Q SESSION (from the server) during that 3 hour wait.
>
> If you see BYTES SENT on one of the sessions to this client getting
> larger and larger during the wait, that's the server sending the
> metadata down to the client. In that case yes, journaling will help.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> Behalf Of Tim Brown
> Sent: Thursday, September 09, 2010 5:26 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] long time for client backup
>
> Would the journal service help
>
> Tim
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> Behalf Of Clark, Margaret
> Sent: Thursday, September 09, 2010 4:48 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: long time for client backup
>
> I bet you've got a lot of little files on at least one of the
> drives. The three hours is used comparing all those little darlings
> with the TSM server's idea of things, before anything gets backed up
> at all. - Margaret Clark
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> Behalf Of Tim Brown
> Sent: Thursday, September 09, 2010 11:41 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] long time for client backup
>
> Client backup starts 8:30PM, It takes 3 hours to get to first
> processed message
> ANS1898I ***** Processed 500 files *****
>
> I restarted the server, no difference, It happens to be a Windows
> 2003 cluster.
>
> Any idea why it takes so long.
>
> 09/08/2010 20:33:09 --- SCHEDULEREC OBJECT BEGIN NT_WKD_OFFCL 09/08/
> 2010 20:30:00 09/08/2010 20:33:11 Incremental backup of volume '\\office
\d$'
> 09/08/2010 20:33:11 Incremental backup of volume '\\office\q$'
> 09/08/2010 20:33:11 Incremental backup of volume '\\office\e$'
> 09/09/2010 00:32:24 ANS1898I ***** Processed 500 files *****
> 09/09/2010 00:32:25 ANS1898I ***** Processed 1,000 files *****
>
>
> Tim Brown
> Systems Specialist - Project Leader
> Central Hudson Gas & Electric
> 284 South Ave
> Poughkeepsie, NY 12601
> Email: tbrown AT cenhud DOT com <<mailto:tbrown AT cenhud DOT com>>
> Phone: 845-486-5643
> Fax: 845-486-5921
> Cell: 845-235-4255
|
