I would also like some info on this subject. I have tried to figure out the sizing spreadsheet from the Redbook SG24-5416 support material. I was wandering if anyone had used this and got an acceptable answer.
Cheers Andy -----Original Message----- From: Bill Mansfield [mailto:[EMAIL PROTECTED]] Sent: 04 April 2002 00:55 To: [EMAIL PROTECTED] Subject: Re: TSM Server Sizing The other factor is storage growth. You probably want your TSM server architecture to last awhile, and I've seen estimates ranging from 50-300% storage CAGR (and consistently seen the estimates exceeded). There are several approaches: - Buy the biggest, most scalable stuff you can afford, and hope for the best. This maximizes the upfront cost, but minimizes the downstream cost. You might get promoted before you run out of capacity. - Buy what you think you will need for the next little while, and plan to upgrade. This works better for servers than libraries, and you can usually find a use for an outgrown server. Also, server price/performance increases much faster than library price/capacity. - Plan to grow modularly with lots of TSM servers. Even TSM can't scale a single server to extremely large environments, and sometimes you're better off biting the bullet and architecting for multiple servers from the getgo. _____________________________ William Mansfield Senior Consultant Solution Technology, Inc "Seay, Paul" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 04/03/2002 04:50 PM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Re: TSM Server Sizing The number of servers and amount of storage mean nothing in my opinion. The issues of what type of storage it is, how many files on the servers, what type of workload the server is, what type of server it is, what type of network connection the server has, what is the backup window, and what bandwidth is in the network are more interesting issues in the sizing. If they are all Gigabit, SAN connected ESS disk, and high end servers then the answer is much easier to calculate. This is not something you just throw into a calculator and bing comes the answer. You have to model the environment, categorize the data and servers, figure out the critical path, and then you have a hope of configuring a solution. -----Original Message----- From: Brenda Collins [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 03, 2002 11:51 AM To: [EMAIL PROTECTED] Subject: TSM Server Sizing Hi! Does anyone have any good tips on sizing a TSM server appropriately? I do have the sizing tool but there is so much manual work in trying to populate that to get any information, particularly when you don't have documentation for every environment. I would welcome some comparisons if you care to share. I will have automated tape libraries at each location also, ranging from a L180, L700 or Powderhorn. I have 5 different sites to size: 1.) 40 servers - 1.5 tb storage total 2.) 50 servers - 1 tb storage total 3.) 300 servers - 11 tb. storage 4.) 125 servers - 6 tb. storage 5.) Moving from Mainframe to Unix - and merging two different backup environments into one. TSM on OS/390 - Current occupancy is 18 TB, TSM database = 18gb Upstream - 325 clients Thanks in advance for any advice you can offer. Brenda Collins Storage Administrator ING - Americas Infrastructure Services (612) 342-3839 (Phone) (612)510-0187 (Pager) [EMAIL PROTECTED] ________________________________________________________________________ This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________ DISCLAIMER: The information contained in this e-mail is confidential and may be privileged. It is intended for the addressee only. If you are not the intended recipient, please delete this e-mail immediately. The contents of this e-mail must not be disclosed or copied without the sender's consent. We cannot accept any responsibility for viruses, so please scan all attachments. The statements and opinions expressed in this message are those of the author and do not necessarily reflect those of the company. The company does not take any responsibility for the views of the author. ________________________________________________________________________ This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________
