Lawrence, you're calculations are off a little bit. You're saying that you have 22,760,941 files, while Gerald is saying he has 625,000,000... factor of ~27... 27*12 = 324GB. (Even at 66% utilization, 324GB is a bit big for a TSM database.)
Gerald, you're probably going to need to look at multiple TSM servers, which isn't as bad as it used to be. With the Library Sharing/Drive Sharing/Scratch Pool Sharing features that were introduced in 3.1+, you should be able to avoid some of headaches that mutliple servers used to involve (servers sharing a 3494 stomping over each others tapes, anyone? ;-) On Fri, 2002-04-26 at 14:57, Lawrence Clark wrote: > Hi: > We have an assigned capacity on our DB of 11,760 MB, of which 66.5 % is currently >in use. We have 22760941 files, which represent 4953359.67 MB in physical >storage, and includes copypool data. This are actual numbers that do not jive with >your calculations. > > > >>> [EMAIL PROTECTED] 04/26/02 03:08PM >>> > My environment could be up to 25TB and 625,000,000 files. According to the > TSM 4.2 Admin Guide to calculate the size of my DB I multiply that by 600 > bytes.. > > 625,000,000 * 600 = 375,000,000,000 bytes = 375,000,000 KB = 375,000 MB = > 375 GB > > There also needs to be an offsite copypool of this data.. According to the > TSM 4.2 Admin Guide: > > 625,000,000 * 200 = 125,000,000,000 bytes = 125GB > > So my DB needs to be 500GB, yikes.. > > How big can one scale a single TSM server installation up to before you need > to start thinking about additional TSM servers? I.e. in this instance can my > TSM server even handle this amount of data? How much could it handle? > > Gerald Wichmann > Sr. Systems Development Engineer > Zantaz, Inc. > 925.598.3099 w > 408.836.9062 c
signature.asc
Description: This is a digitally signed message part
