Immediate quick thought is that whilst much of the client backup activity for a TSM Server may well be overnight, most TSM Servers perform their not-insignificant essential housekeeping during the day which, depending upon the load of your TSM Server, may be a considerable drain on the system's I/O resources (disk > tape migration, expiration, reclamation etc).
/David Mc London, UK -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Haberstroh, Debbie (IT) Sent: 18 September 2009 16:36 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM architecture Hi All, My current environment is TSM 5.5.3, 1 library manager, 3 database servers. These are installed on a P550 AIX 5.3 system in separate LPAR's. We have 355 clients, 200 + are active. My current TSM databases are 100GB, 65-82% utilized. We are going to be doing a large business object installation which will add 30-50 new clients including multiple Oracle databases. Our proposal was to add an additional TSM server to handle the new requirements. We have a new "architect" that is not very familiar with TSM and his proposal is to "stack" TSM on another server that is running a different application. His argument is that TSM does most of it's work at night and the application (which one is TBD) does most of it's work during the day. >From what I know, due to TSM's resource utilization, it should be on it's own hardware. Has anyone tried to do this and what were your results? I would love to get some good arguments to take back that would support our original position to install on separate hardware. Thanks to everyone for your ideas. Debbie Haberstroh TSM Server Administration No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.409 / Virus Database: 270.13.102/2377 - Release Date: 09/18/09 07:49:00