I received this information from a StorageTek engineer. My primary
question to them was how to size it to ensure that I could drive the number
of tape drives we were configuring and get the top performance possible.
I was being lazy and didn't have time to gather information on 500 servers
to use the Tivoli planning tool. I figured that they are installing these
systems all over the place, there has to be some ballpark numbers on what
installations are being set up as and what configurations have worked the
best.
I did have Tivoli size a smaller site I have and their recommendations came
out the same as using this process.
Have a good day!
Brenda Collins
ING - Americas Infrastructure Services
(612) 342-3839 (Phone)
(
[EMAIL PROTECTED]
"Joshua S.
Bassi" To: [EMAIL PROTECTED]
<[EMAIL PROTECTED] cc:
OM> Subject: Re: TSM and Capacity Planning
Sent by:
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
IST.EDU>
04/15/2002
12:37 PM
Please respond
to "ADSM: Dist
Stor Manager"
I have never seen this rule of thumb for sizing a TSM servers CPU.
Where did you find this rule of thumb?
--
Joshua S. Bassi
Sr. Solutions Architect @ rs-unix.com
IBM Certified - AIX/HACMP, SAN, Shark
Tivoli Certified Consultant- ADSM/TSM
Cell (415) 215-0326
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
Brenda Collins
Sent: Tuesday, April 09, 2002 11:11 AM
To: [EMAIL PROTECTED]
Subject: Re: TSM and Capacity Planning
Hi!
Here are some tips that I received this week from a StorageTek Engineer.
The final recommendation for server size that he made was the same that
the
Tivoli Engineer had provided without having to go through the entire
exercise of tracking all servers, their disk size requirements,
databases,
etc.
The official rule of thumb on sizing is 10Mhz for per each MB/sec's for
the
backup solution. So if you had 10 9840B's drives (each with native
transfer
rate of 19 MB's) and had the network matched on the front end to match
the
required data rate that would equal 190MB/sec. I assume 2:1 compression
which would then be 380 MB/sec or 3800Mhz of Cpu. Just remember this is
to
build so there isn't a bottleneck, having less will work, but you wont
get
the best performance that is possible. Usually the network is a limiting
bottleneck like GB ethernet is about 60 MB/sec and if you only have one,
it
doesnt matter how many tape drives I have because the best rate I can
get
to
the drives is 60MB/sec or 600 Mhz worth of CPU's.
Brenda Collins
ING - Americas Infrastructure Services
(612) 342-3839 (Phone)
[EMAIL PROTECTED]
"Farren Minns"
<fminns@WILEY. To: [EMAIL PROTECTED]
CO.UK> cc:
Sent by: Subject: TSM and Capacity
Planning
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
IST.EDU>
04/09/2002
10:56 AM
Please respond
to "ADSM: Dist
Stor Manager"
Hello again TSMers
I am currently in the process of preparing a capacity planning document
for
our TSM set-up so that I can at least try to estimate when our Server
will
become pushed to its limits.
I was wondering who else has done this recently and if there are any
good
sources of inf. on the net that may be of help to me.
At the moment we have TSM Server 3.7.3.8 running on a Sun Solaris E250
(400Mhz, 1GB memory). We have 28 client running on Solaris, OS/2, NT and
one Linux for good measure. We have one 3494 tape library housing two
3590
tape drives (J Tapes - 20Gb compress, 10 uncompressed).
I can easily work out approx. how many tapes we are going to need; how
much
free space we have in the library; how much disk space we may need for
the
database, log etc. But the thing I need help with is figuring out how
much
client data we can back up within a certain window. All clients seem to
have different rates at which they can process data; some machines are
remote; some use compression etc. etc. etc. I'm am quite new to this and
would be interested in other peoples experiences in doing this kind of
thing.
I guess there are so many questions that to sit here and type them all
would be foolish. I'm more interested in finding out what the crucial
questions I should be asking are (are you still with me, I know I'm
rambling now).
Also, I'm interested in learning more about the tuneable parameters
within
TSM (Server and Client); what sort of things I could do to improve data
throughput, database performance, tape performance etc.
Basically, any help, pointers etc regarding this type of thing would be
very much appreciated.
Thanks very much
All the best
Farren Minns - Trainee Solaris and TSM system admin
John Wiley & Sons
