That depends more on the number of disks you writing to and the type of
san you are using. 

For instance if you are using an SVC or other virtualization solution
your 900 gb may already be striped across more than 30 disks. Then
partitioning may not be necessary.
If you are using a direct connect solution you may see better
performance if you create multiple luns across  a number of arrays. In
this instance you are better off partitioning them as the sizes of the
physicals disks presented to the system.

We are using 3 1 tb luns being served by an SVC for diskpools to one TSM
server. But each diskpool varies in size from 100gb to 1.5 tb. All the
diskpools have 25-50gb volumes defined and each diskpool has volumes on
each lun. 



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Dollens, Bruce
Sent: Thursday, July 31, 2008 9:16 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: New TSM Layout

We are in the process of designing our new TSM server. As part of this
we are also going to give it new SAN drive space. 

 

Currently we have 661 Gig in our disk pool and we are upping that to 900
Gig. What our questions is how should we partition that? Our current
pool is in 7 partitions but I was thinking more like 3 or 4 partitions.
Are there any pro's/con's with going with fewer disk partitions?