Re: Slow restore of large file to Win2003 client.
Thank you Andy. That looks like the same problem we are having. Time for an upgrade. Larry -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Raibeck Sent: Thursday, October 11, 2007 10:25 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Slow restore of large file to Win2003 client. Have a look at APAR IC49469 (follow the link in my sig and enter the APAR number); this might be the problem you are seeing. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageMan ager.html 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" wrote on 10/11/2007 07:10:05 AM: > Environment: > TSM server AIX 5.3 P570 > TSM 5.3.3.0 > Client Win2003 HP Proliant DL585 64GB > TSM client 5.3.2.2 > > We restored 178 GB in 7.5 hours. The restore consisted of 1 file that > is 160 GB and 25 files totaling 18 GB. The 160 GB file was on 1 LTO3 > tape in a L700 library with a 2 GB fibre connection. The restore > initially started running at over 30 GB per hour and gradually slowed to > less than 20 GB per hour by the time it completed for the large file. > Then the 25 smaller files (18 GB) restored at the faster speed. The > workload was light on the TSM server and the client. Can anyone provide > some insight as to what may cause a large restore to decrease in > throughput? > > Thanks, > Larry McNutt > The Timken Company > > Date/TimeMessage > > -- > 10/10/07 17:50:13 ANE4955I (Session: 92718, Node: FSPHSAPRCO) Total > number > of objects restored:26(SESSION: 92718) > 10/10/07 17:50:13 ANE4959I (Session: 92718, Node: FSPHSAPRCO) Total > number > of objects failed: 0(SESSION: 92718) > 10/10/07 17:50:13 ANE4961I (Session: 92718, Node: FSPHSAPRCO) Total > number > of bytes transferred: 178.31 GB(SESSION: 92718) > 10/10/07 17:50:13 ANE4963I (Session: 92718, Node: FSPHSAPRCO) Data > transfer > time:13,548.81 sec(SESSION: 92718) > 10/10/07 17:50:13 ANE4966I (Session: 92718, Node: FSPHSAPRCO) > Network data > transfer rate:13,800.16 KB/sec(SESSION: > 92718) > 10/10/07 17:50:13 ANE4967I (Session: 92718, Node: FSPHSAPRCO) > Aggregate > data transfer rate: 6,886.06 KB/sec(SESSION: > 92718) > 10/10/07 17:50:13 ANE4964I (Session: 92718, Node: FSPHSAPRCO) > Elapsed > processing time:07:32:32(SESSION: > 92718) > 10/10/07 17:51:07 ANR0403I Session 92718 ended for node FSPHSAPRCO > (WinNT).(SESSION: 92718) > > - > This message and any attachments are intended for the individual or > entity named above. If you are not the intended recipient, please > do not forward, copy, print, use or disclose this communication to > others; also please notify the sender by replying to this message, > and then delete it from your system. The Timken Company / The > Timken Corporation
Re: Slow restore of large file to Win2003 client.
Have a look at APAR IC49469 (follow the link in my sig and enter the APAR number); this might be the problem you are seeing. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html 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" wrote on 10/11/2007 07:10:05 AM: > Environment: > TSM server AIX 5.3 P570 > TSM 5.3.3.0 > Client Win2003 HP Proliant DL585 64GB > TSM client 5.3.2.2 > > We restored 178 GB in 7.5 hours. The restore consisted of 1 file that > is 160 GB and 25 files totaling 18 GB. The 160 GB file was on 1 LTO3 > tape in a L700 library with a 2 GB fibre connection. The restore > initially started running at over 30 GB per hour and gradually slowed to > less than 20 GB per hour by the time it completed for the large file. > Then the 25 smaller files (18 GB) restored at the faster speed. The > workload was light on the TSM server and the client. Can anyone provide > some insight as to what may cause a large restore to decrease in > throughput? > > Thanks, > Larry McNutt > The Timken Company > > Date/TimeMessage > > -- > 10/10/07 17:50:13 ANE4955I (Session: 92718, Node: FSPHSAPRCO) Total > number > of objects restored:26(SESSION: 92718) > 10/10/07 17:50:13 ANE4959I (Session: 92718, Node: FSPHSAPRCO) Total > number > of objects failed: 0(SESSION: 92718) > 10/10/07 17:50:13 ANE4961I (Session: 92718, Node: FSPHSAPRCO) Total > number > of bytes transferred: 178.31 GB(SESSION: 92718) > 10/10/07 17:50:13 ANE4963I (Session: 92718, Node: FSPHSAPRCO) Data > transfer > time:13,548.81 sec(SESSION: 92718) > 10/10/07 17:50:13 ANE4966I (Session: 92718, Node: FSPHSAPRCO) > Network data > transfer rate:13,800.16 KB/sec(SESSION: > 92718) > 10/10/07 17:50:13 ANE4967I (Session: 92718, Node: FSPHSAPRCO) > Aggregate > data transfer rate: 6,886.06 KB/sec(SESSION: > 92718) > 10/10/07 17:50:13 ANE4964I (Session: 92718, Node: FSPHSAPRCO) > Elapsed > processing time:07:32:32(SESSION: > 92718) > 10/10/07 17:51:07 ANR0403I Session 92718 ended for node FSPHSAPRCO > (WinNT).(SESSION: 92718) > > - > This message and any attachments are intended for the individual or > entity named above. If you are not the intended recipient, please > do not forward, copy, print, use or disclose this communication to > others; also please notify the sender by replying to this message, > and then delete it from your system. The Timken Company / The > Timken Corporation
Slow restore of large file to Win2003 client.
Environment: TSM server AIX 5.3 P570 TSM 5.3.3.0 Client Win2003 HP Proliant DL585 64GB TSM client 5.3.2.2 We restored 178 GB in 7.5 hours. The restore consisted of 1 file that is 160 GB and 25 files totaling 18 GB. The 160 GB file was on 1 LTO3 tape in a L700 library with a 2 GB fibre connection. The restore initially started running at over 30 GB per hour and gradually slowed to less than 20 GB per hour by the time it completed for the large file. Then the 25 smaller files (18 GB) restored at the faster speed. The workload was light on the TSM server and the client. Can anyone provide some insight as to what may cause a large restore to decrease in throughput? Thanks, Larry McNutt The Timken Company Date/TimeMessage -- 10/10/07 17:50:13 ANE4955I (Session: 92718, Node: FSPHSAPRCO) Total number of objects restored:26(SESSION: 92718) 10/10/07 17:50:13 ANE4959I (Session: 92718, Node: FSPHSAPRCO) Total number of objects failed: 0(SESSION: 92718) 10/10/07 17:50:13 ANE4961I (Session: 92718, Node: FSPHSAPRCO) Total number of bytes transferred: 178.31 GB(SESSION: 92718) 10/10/07 17:50:13 ANE4963I (Session: 92718, Node: FSPHSAPRCO) Data transfer time:13,548.81 sec(SESSION: 92718) 10/10/07 17:50:13 ANE4966I (Session: 92718, Node: FSPHSAPRCO) Network data transfer rate:13,800.16 KB/sec(SESSION: 92718) 10/10/07 17:50:13 ANE4967I (Session: 92718, Node: FSPHSAPRCO) Aggregate data transfer rate: 6,886.06 KB/sec(SESSION: 92718) 10/10/07 17:50:13 ANE4964I (Session: 92718, Node: FSPHSAPRCO) Elapsed processing time:07:32:32(SESSION: 92718) 10/10/07 17:51:07 ANR0403I Session 92718 ended for node FSPHSAPRCO (WinNT).(SESSION: 92718) - This message and any attachments are intended for the individual or entity named above. If you are not the intended recipient, please do not forward, copy, print, use or disclose this communication to others; also please notify the sender by replying to this message, and then delete it from your system. The Timken Company / The Timken Corporation
