Unfortunately disk pools with a device class of DISK get fragmented and
will incur a higher overhead penalty the longer they exist (without data
moving off to tape).  I had a customer try this configuration and it
ended up blowing up in their face.


--
Joshua S. Bassi
IBM Certified - AIX 4/5L, SAN, Shark
Tivoli Certified Consultant -ADSM/TSM
eServer Systems Expert -pSeries HACMP

AIX, HACMP, Storage, TSM Consultant
Cell (831) 595-3962
jbassi AT ihwy DOT com

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Andy Carlson
Sent: Thursday, January 09, 2003 11:09 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM Disk Pool Management


We have given this a little bit of thought also.  You would not need to
use type=file - just enlarge your current disk pool.  Expire will age
the files out of there.  The only thing to watch, is for it to be
getting full, and more disk needs to be added.


Andy Carlson                                    |\      _,,,---,,_
Senior Technical Specialist               ZZZzz /,`.-'`'    -.  ;-;;,_
BJC Health Care                                |,4-  ) )-,_. ,\ (  `'-'
St. Louis, Missouri                           '---''(_/--'  `-'\_)
Cat Pics: http://andyc.dyndns.org/animal.html


On Thu, 9 Jan 2003, Hokanson, Mark wrote:

> We are considering creating an extremely large TSM disk storage pool
> (IE: 1-10TB). The goal being to eliminate going to tape. Does anyone
> have any really BIG disk pools? Are there tools available for managing

> large TSM disk pools over time. (IE: Reclamation, Aging Data, etc) The

> documentation from Tivoli suggests that we need to set it up as a
> device type=FILE. What are the drawbacks using this approach? Is
> performance dramatically impacted? etc...
>
> Thanks in advance,
>
> Mark Hokanson
> Thomson Legal & Regulatory
>