I would think the best way to keep TSM from getting into trouble would
be to limit the number of mounts.
This will keep you from having too many 10G files going at any one time.
OR 
Increase the file size so that you limit how many volumes you manage in
TSM to keep the db size down.  2700 really shouldn't be that much of a
problem for TSM.  It all depends on how big your DB is, how much RAM you
have, etc.  27 TB is really not much at all for a rightly sized TSM
server.  Also, your hardware and OS platform will have a lot to do with
it.  

See Ya'
Howard

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Michael Glad
> Sent: Thursday, September 18, 2008 3:15 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] Volume size on sequential disk storage pools
> 
> Hello TSM'ers, are there any recommendations/experiences concerning
> volume size/
> maximum number of volumes on sequential disk storage pools?
> 
> On our largest TSM server, we currently have a 27T pool consisting of
> 10G
> volumes => some 2700 volumes. I chose the 10 gig size a couple of
years
> ago
> after reading an IBM paper.
> 
> Although there currently doesn't seem to be any major performance
> problems, I wonder if there's a limit to the number of volumes after
> which TSM may get into troubles.
> 
> So I would be glad to learn what volume size / number of volumes other
> TSM sites using sequential disk volumes use.
> 
>       -- Michael