Allen, I haven't gone back and looked at the actual memory footprint, sorry. (These aren't massive servers like yours!) The post from Stefan is as good as any info I have. I've been using this as a rule of thumb:
- 12G min for a trivial-size TSM server (i.e. <=50 clients), without dedup or the ISC - 16G for larger without dedup - more for dedup, + 64bit Windows if that's the server platform + 4G if the ISC is on the same machine (I havent' seen a V6 server yet with a DB bigger than 500G, can't wait!) W -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Allen S. Rout Sent: Monday, October 17, 2011 8:54 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] vtl versus file systems for pirmary pool On 10/14/2011 04:47 PM, Prather, Wanda wrote: > I have 2 others (smaller DB's ) that I've converted from production > 5.5 to 6.2, and have no qualms about recommending it to anybody > (assuming the server hardware has the required memory). It's been > stable for them. Please elaborate on your experiences w.r.t. memory footprint? It's my major planning unknown; I'm musing about instance count vs. size. - Allen S. Rout
