ypcat
ADSM.ORG Member
Tsm 6
Thanks guys,
I'm anxious to get to TSM 6.x for many reasons including those outlined above but I have a petabyte or so of data and don't want to deal with too many issues during and after the switch. Because this is a new database engine for ADSM/TSM there are bound to be quite a few issues... So I guess I'll wait for the most stable iteration for as long as I can unless folks here start saying it's rock solid.
There is a pressing reason for me to switch however, and that leads to another question; there's a known bug in TSM 5.x where a device class type of file which uses more than a single file system (directory: /usr/local/tsm/fs1,usr/local/tsm/fs2) for a storage pool cannot dynamically create new volumes as needed with the maxscratch parameter after one of the file systems is full. This leads to an architectural limitation of 32 TB per disk based storage pool (in AIX) unless I want to create my own volumes manually.
Does anyone know if this been fixed in TSM 6?
Thanks guys,
I'm anxious to get to TSM 6.x for many reasons including those outlined above but I have a petabyte or so of data and don't want to deal with too many issues during and after the switch. Because this is a new database engine for ADSM/TSM there are bound to be quite a few issues... So I guess I'll wait for the most stable iteration for as long as I can unless folks here start saying it's rock solid.
There is a pressing reason for me to switch however, and that leads to another question; there's a known bug in TSM 5.x where a device class type of file which uses more than a single file system (directory: /usr/local/tsm/fs1,usr/local/tsm/fs2) for a storage pool cannot dynamically create new volumes as needed with the maxscratch parameter after one of the file systems is full. This leads to an architectural limitation of 32 TB per disk based storage pool (in AIX) unless I want to create my own volumes manually.
Does anyone know if this been fixed in TSM 6?
