Or, just do it the old way - once your copies are synced in the new copy
pool, start deleting volumes in the old pool.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: Wednesday, March 10, 2004 2:50 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Copy Pool expiration conundrum

>I tried this once, and the 'move nodedata' processes terminated
immediately,
>reporting successful completion but not moving any data. It turns out
that
>'move nodedata' for copy storage pools requires mounting the copy
storage
>pool volumes containing the data to be moved; it will not obtain input
>data from primary storage pool volumes as reclamation and 'move data'
>processes will.

Indeed.  In my notes on the command, I include:

                                        As of 2003/11 the Reference
Manual fails
                                        to advise what the Tech Guide
does: that
                                        the Access mode of the volumes
must be
                                        READWRITE or READONLY, which
precludes
                                        OFFSITE and any possibility of
onsite
                                        volumes standing in for the
offsite
                                        vols.

You obviously need to buy more tapes and library extensions from that
there
vendor.  :-)

    Richard