Export/import is really designed to move data from one adsm server to
     another adsm server.  If you want to move data from one storage pool
     to another you can move it a volume at a time using move data.  We use
     a dasd storage pool like a cache to backup all our client data then
     each day migrate that data to a tape storage pool.  For us to move to
     a new storage pool is real easy, we just start migrating the cache to
     the new tape storage pool and then start moving the data from the old
     tape storage pool to the new tape storage pool a volume at a time.
     You can even wait a month or so to let some of the data expire before
     you start moving it, that way you don't have to move so much data.
     Jim Sporer



______________________________ Reply Separator _________________________________
Subject: Moving storage pools
Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>  at IPNET
Date:    1/21/99 1:22 PM


We will be replacing our 3570 tape libraries with a 3575 soon, and need to
plan our migration path.  In the past, we've used the export/import
function to move nodes between physical libraries.  Is that the right
method, or is there a better and/or easier way?


====================================================================
Bo R. Ossinger                 phone: 509-335-0920
Washington State University    fax:   509-335-6635,,,50920
Information Technology         mailto:ossinger AT wsu DOT edu
Production Support Systems     http://www.wsu.edu/prod_supp/Pss.html
PO Box 641222
Pullman, WA  99164-1222
====================================================================