You can't have one storage pool span the libraries. You have to have one
pool for each library. And, unless I'm missing something, different Device
Classes (not Types) for each library.
What you can have one pool point to the other as a "Next Storage Pool".
That way, when the first one fills up, it directs the data to the second
one. You could set the high and low migration thresholds so that data is
sent to the second pool, too, keeping some space free in the first one (for
reclaimation, etc). It would look like this: (This is using 3995 optical
jukeboxes, but would be the same for tape)
Storage Device Estimated Pct Pct High Low Next
Pool Name Class Name Capacity Util Migr Mig Mig Storage
(MB) Pct Pct Pool
----------- ---------- ---------- ----- ----- ---- --- -----------
ARCHIVEPOOL DISK 0.0 0.0 0.0 90 70
ARCHIVEPOOL DISK 0.0 0.0 0.0 90 70
BACKUPPOOL DISK 0.0 0.0 0.0 50 0
OFFSITEPOOL OFFOPTICAL 449,873.8 98.4
OPTICALPOOL OPTICAL 395,168.7 69.1 69.4 90 70 OPTICALPOO-
L2
OPTICALPOO- OPTICAL2 268,453.3 76.5 76.9 90 70
L2
OPTPOOL DISK 1,600.0 14.6 14.6 90 0 OPTICALPOOL
SPACEMGPOOL DISK 0.0 0.0 0.0 90 70
Data comes into OPTPOOL, and migrates to OPTICALPOOL. When OPTICALPOOL
hits 90% full, migration kicks in and pushes data to OPTICALPOOL2.
Obviously, I hit the same problem. If you could have both libraries in the
same pool, ADSM could ask for a tape from Library 1 to mount in a drive in
Library 2, which would require manually moving the tape. Which , in my
opinion, defeats having a Tape Library.
Nick Cassimatis
Distributed Systems Management / Storage Management
RTP, NC
919-254-7302 T/L 444-7302
nickpc AT us.ibm DOT com
If you don't have the time to do it right the first time, where will you
find the time to do it again?
|