No, our TSM server is one of the few servers we run that has its own iron.
It's a dual 2GHz Xeon, 2.5G RAM, RHEL 3.0, DB on local 15k RPM RAID 1, disk
pools on SAN (RAID 5 array, 10k RPM).

-Ken
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Timothy Lin
Sent: Friday, March 10, 2006 10:35 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Journaling/Linux

That's very good performance, out of curiosity,
is your TSM server also running on top of VM ?
I know VM instances can talk to each other over the memory instead of
over the net

Tim.

Mueller, Ken wrote:

>The file server is a virtual machine on one of our ESX servers. The VM is a
>single processor (2.5GHz Xeon), 768M RAM - SAN storage controlled by a
>FAStT700.
>
>The secret ingredient may lie in the often shunned 'memoryefficient yes' in
>the client's dsm.opt.
>-Ken
>
>-----Original Message-----
>From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
>Troy Frank
>Sent: Thursday, March 09, 2006 1:18 PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: Journaling/Linux
>
>Ditto.  on one of our bigger file servers, ~1.3million files, 2-cpu
>2.4ghz, 2.5GB RAM, SAN attached storage (that gets ~100MB/sec
>throughput), it take us 45min to get through a backup.  This seems to be
>almost 20X that fast.
>
>
>
>