Stephen,

you already found the *best* answer yourself - yes, set new stgpool as
next to existing one and lower migration thresholds to 0. Just some
additional remarks:
set the "old" pool(s) as read-only and (optional) set maxscratch=0. This
would prevent nodes to fill the pool while you are trying to drain it to
the next one - might be endless :)
later when you have time (even it is immediately) change all the
references to "old" pool(s).
Yes, this would also reclaim the tapes but will also recreate the
aggregates. The latter would not be performed if you use 'move data'! And
you should perform "moves" for each tape while migration is automatic
server-driven process.
I hope this sets the line straight.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:        Adding a second library

I've added a second 7337 library to our ADSM system (15 DLT robot with 2
drives). I've got the system seeing the library, and I have a new
devclass defined with the new library.

What I would like to do is have two of our stgpools (AFS_TAPE_POOL and
COPYPOOL) we have defined use this new library, with the others staying
in the original library. I can't change the devclass on a stgpool with
the update stgpool command, so I'd have to create a new stgpool.

What's the best way to get the data in the old stgpool out of that pool
into the new pool? Should I just set NEXTpool to point to the new pool
and set the migration level to 0%? Then when all the data is moved out
of the original pool delete the pool? (This would give the added benefit
of reclaiming all wasted tape space at the same time....)

Steve Cochran
Dartmouth College