Tsm server possibly limiting backup performance

2011-05-27 Thread Lee, Gary D.
Tsm server 6.2.2 
OS redhat enterprise linux 6.0 
Client tdp for exchange, sqlserver, and backup archive client

Client connected via 1 gb ethernet connection.

In my experience, I yhave never been able to se throughput of much more than 
200 mb/s during a tsm backup, whether tdp or regular client.
I wonder, is TSM limiting a single session's bandwidth so as to insure 
availability for other client sessions which might begin; i.e. prevent one 
backup stream from monopolizing the server's network connection?

I have run ftp  and other tests to the server, and achieved throughput of 
around 800 mb/s over the same connection.



Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310

 

Re: Tsm server possibly limiting backup performance

2011-05-27 Thread Richard Rhodes
A little more explanation is going to be needed.  A 1GB ethernet is not
going to give 800mb/s, let alone 200mb/s.  1GB ethernet is only going to
provide one direction throughput of 110mb/s.  Do you mean a 10gb ethernet
connection?





From:   Lee, Gary D. g...@bsu.edu
To: ADSM-L@VM.MARIST.EDU
Date:   05/27/2011 09:35 AM
Subject:Tsm server possibly limiting backup performance
Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU



Tsm server 6.2.2
OS redhat enterprise linux 6.0
Client tdp for exchange, sqlserver, and backup archive client

Client connected via 1 gb ethernet connection.

In my experience, I yhave never been able to se throughput of much more
than 200 mb/s during a tsm backup, whether tdp or regular client.
I wonder, is TSM limiting a single session's bandwidth so as to insure
availability for other client sessions which might begin; i.e. prevent one
backup stream from monopolizing the server's network connection?

I have run ftp  and other tests to the server, and achieved throughput of
around 800 mb/s over the same connection.



Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310





-
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.


Re: Tsm server possibly limiting backup performance

2011-05-27 Thread David McClelland
To make sure we're all talking the same language here, can we agree that 'b' 
means 'bit' and 'B' means 'byte'? This conversation could get very confusing 
otherwise...

/DMc

On 27 May 2011, at 15:09, Richard Rhodes rrho...@firstenergycorp.com wrote:

 A little more explanation is going to be needed.  A 1GB ethernet is not
 going to give 800mb/s, let alone 200mb/s.  1GB ethernet is only going to
 provide one direction throughput of 110mb/s.  Do you mean a 10gb ethernet
 connection?
 
 
 
 
 
 From:   Lee, Gary D. g...@bsu.edu
 To: ADSM-L@VM.MARIST.EDU
 Date:   05/27/2011 09:35 AM
 Subject:Tsm server possibly limiting backup performance
 Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
 
 
 
 Tsm server 6.2.2
 OS redhat enterprise linux 6.0
 Client tdp for exchange, sqlserver, and backup archive client
 
 Client connected via 1 gb ethernet connection.
 
 In my experience, I yhave never been able to se throughput of much more
 than 200 mb/s during a tsm backup, whether tdp or regular client.
 I wonder, is TSM limiting a single session's bandwidth so as to insure
 availability for other client sessions which might begin; i.e. prevent one
 backup stream from monopolizing the server's network connection?
 
 I have run ftp  and other tests to the server, and achieved throughput of
 around 800 mb/s over the same connection.
 
 
 
 Gary Lee
 Senior System Programmer
 Ball State University
 phone: 765-285-1310
 
 
 
 
 
 -
 The information contained in this message is intended only for the
 personal and confidential use of the recipient(s) named above. If
 the reader of this message is not the intended recipient or an
 agent responsible for delivering it to the intended recipient, you
 are hereby notified that you have received this document in error
 and that any review, dissemination, distribution, or copying of
 this message is strictly prohibited. If you have received this
 communication in error, please notify us immediately, and delete
 the original message.


Re: Tsm server possibly limiting backup performance

2011-05-27 Thread Paul Fielding
I think clarification is needed on mb/s vs. MB/s.

a 1gb (gigabit) (note lowercase) connection will certainly do 800 mb/s
(megabit/s).  it won't, however, do 800 MB/s (megabyte/s)

Paul


On Fri, May 27, 2011 at 8:09 AM, Richard Rhodes rrho...@firstenergycorp.com
 wrote:

 A little more explanation is going to be needed.  A 1GB ethernet is not
 going to give 800mb/s, let alone 200mb/s.  1GB ethernet is only going to
 provide one direction throughput of 110mb/s.  Do you mean a 10gb ethernet
 connection?





 From:   Lee, Gary D. g...@bsu.edu
 To: ADSM-L@VM.MARIST.EDU
 Date:   05/27/2011 09:35 AM
 Subject:Tsm server possibly limiting backup performance
 Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU



 Tsm server 6.2.2
 OS redhat enterprise linux 6.0
 Client tdp for exchange, sqlserver, and backup archive client

 Client connected via 1 gb ethernet connection.

 In my experience, I yhave never been able to se throughput of much more
 than 200 mb/s during a tsm backup, whether tdp or regular client.
 I wonder, is TSM limiting a single session's bandwidth so as to insure
 availability for other client sessions which might begin; i.e. prevent one
 backup stream from monopolizing the server's network connection?

 I have run ftp  and other tests to the server, and achieved throughput of
 around 800 mb/s over the same connection.



 Gary Lee
 Senior System Programmer
 Ball State University
 phone: 765-285-1310





 -
 The information contained in this message is intended only for the
 personal and confidential use of the recipient(s) named above. If
 the reader of this message is not the intended recipient or an
 agent responsible for delivering it to the intended recipient, you
 are hereby notified that you have received this document in error
 and that any review, dissemination, distribution, or copying of
 this message is strictly prohibited. If you have received this
 communication in error, please notify us immediately, and delete
 the original message.



Re: Tsm server possibly limiting backup performance

2011-05-27 Thread Lee, Gary D.
Sorry, thought I had my cases correct.

1 gb (gigabit) ethernet ocnnection.
Ftp and other tests yielded 800 megabit performance,
Tsm sessions average 200 to 250 megabit.
 


Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310

 
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Paul 
Fielding
Sent: Friday, May 27, 2011 10:30 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Tsm server possibly limiting backup performance

I think clarification is needed on mb/s vs. MB/s.

a 1gb (gigabit) (note lowercase) connection will certainly do 800 mb/s
(megabit/s).  it won't, however, do 800 MB/s (megabyte/s)

Paul


On Fri, May 27, 2011 at 8:09 AM, Richard Rhodes rrho...@firstenergycorp.com
 wrote:

 A little more explanation is going to be needed.  A 1GB ethernet is not
 going to give 800mb/s, let alone 200mb/s.  1GB ethernet is only going to
 provide one direction throughput of 110mb/s.  Do you mean a 10gb ethernet
 connection?





 From:   Lee, Gary D. g...@bsu.edu
 To: ADSM-L@VM.MARIST.EDU
 Date:   05/27/2011 09:35 AM
 Subject:Tsm server possibly limiting backup performance
 Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU



 Tsm server 6.2.2
 OS redhat enterprise linux 6.0
 Client tdp for exchange, sqlserver, and backup archive client

 Client connected via 1 gb ethernet connection.

 In my experience, I yhave never been able to se throughput of much more
 than 200 mb/s during a tsm backup, whether tdp or regular client.
 I wonder, is TSM limiting a single session's bandwidth so as to insure
 availability for other client sessions which might begin; i.e. prevent one
 backup stream from monopolizing the server's network connection?

 I have run ftp  and other tests to the server, and achieved throughput of
 around 800 mb/s over the same connection.



 Gary Lee
 Senior System Programmer
 Ball State University
 phone: 765-285-1310





 -
 The information contained in this message is intended only for the
 personal and confidential use of the recipient(s) named above. If
 the reader of this message is not the intended recipient or an
 agent responsible for delivering it to the intended recipient, you
 are hereby notified that you have received this document in error
 and that any review, dissemination, distribution, or copying of
 this message is strictly prohibited. If you have received this
 communication in error, please notify us immediately, and delete
 the original message.



Re: Tsm server possibly limiting backup performance

2011-05-27 Thread Richard Sims
The networking itself is just one element in the overall backup operation...  
You don't say what measurement point you are looking at for your throughput 
numbers.  If it is the Network data transfer rate TSM summary statistic, that 
reflects TSM interacting with the network layer of the operating system, with 
affecters such as TSM TCPWindowsize, Path MTU Discovery where that is in 
effect, etc.  Unexpected, elongated network routing can delay things; but your 
FTP test should have run into that if were a factor...unless conditions are 
changing depending upon time of day.  When a TDP is involved, it can only pass 
data as fast as the back end application provides it.  A traditional B/A backup 
can be impaired by the paging incited by the amount of memory taken by the 
Active files list.  If standard measurement points don't reveal a cause, a 
client trace with a representative data set can be illuminating.

Richard Sims