I've done part of this.  One instance controls the drives 
and, more important, the scratch pool. Since there are no 
clients, there's no disk storage and the DB and Log fit in 
the default space that comes with the installation so the 
reboot time is quite quick whenever maintenance is needed.  
At present, it controls two robots, a 3494 and a 3584, 14 
drives, 8 3590 and 6 3592, and 4 TSM instances.
 

---- Original message ----
>Date: Mon, 15 Aug 2005 13:13:13 +0200
>From: Bernd Wiedmann <Bernd.Wiedmann AT GEK DOT DE>  
>Subject: [ADSM-L] enterprise setup  
>To: ADSM-L AT VM.MARIST DOT EDU
>
>hi everyone,
>
>we are planning to do some enterprise configuration.
>Now, what I have in mind is something like this:
>
>1 TSM-Master-Server, which acts as configuration manager,
>  central event-logger, and administration-server. 5 drives
>  in a storagetek library.
>  maybe hot standby.
>  
>n instances of TSM-Server, which serve the nodes.
>  but, this TSM-Server won't have any tape or disk-storage.
>  because they send all data to the master-server via 
virtual volumes.
>  
>This configuration has the big advantage that the instances 
don't need drives,
>or something like that.
>
>So here are my questions:
>Does anyone has such a environment?
>Does anyone know any pitfalls?
>Does that concept make sense to you?
>
>thanks in advance
>
>best regards
>Bernd Wiedmann
>
>
>
>
>
>Bernd Wiedmann
>IT-Spezialist
>
>Gmünder Ersatzkasse GEK
>Abteilung Information und Kommunikation
>Gottlieb-Daimler-Str. 29
>D-73529 Schwäbisch Gmünd
>
>E-Mail: bernd.wiedmann AT gek DOT de 
>Internet: http://www.gek.de 
>Telefon: +49 (7171) 801-1707
>Telefax: +49 (7171) 801-706
Fred Johanson