Caveat: My last TSM experience was with release 5.3, over a year and a half ago...
Begin at, well, the beginning. The TSM server admin should be watching the buffer pool hit ratio, and expand (or contract) the database buffer pool size to achieve 98% (is that still the ROT?). Similar rules govern the log pool size. If the sum of those is 10 GB, then maybe 12 GB for the total machine size is "reasonable". As in, as reasonable as the 10 GB calculation. As Jay's experience shows, you can get by with a lot less, but he's obviously defined much smaller buffer pools. Mark Wheeler UnitedHealth Group > Date: Wed, 2 Jun 2010 14:26:01 -0400 > From: bren...@gmail.com > Subject: Re: TSM memory requirements > To: LINUX-390@VM.MARIST.EDU > > I've got a TSM server running on Linux under z/VM for backing up > internal test systems and it's happily running in 512 MB of Storage. > If the disk and tape subsystems are fast enough you can make it pretty > small and still be OK. It depends on your daily load. Mine is pretty > light. > > -- > Jay Brenneman > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 _________________________________________________________________ Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
