Re: TSM Disk Pool Management
2003-01-09 10:27:17
I have a customer with 9 TSM servers and around 20TB of disk pool
storage. We use a device class of DISK because data does not stay on
disk, instead it moves off to tape daily.
If you plan to use this large diskpool to permanently store your backup
data, then you should definitely use a devclass of FILE. Why? Because
FILE is sequential and the DISK device class is random. Over time a
DISK storage pool will fragment as expiration occurs and TSM doesn't
automatically do a reorg on it like it can with a sequential FILE disk
pool.
--
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
Hokanson, Mark
Sent: Thursday, January 09, 2003 7:15 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: TSM Disk Pool Management
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
|
|
|