Single "move nodedata" ought to be enough for single node. Depending on
the number of nodes, several moves can be less time consuming than
collocation of the whole stgpool.
"clean archdir" and "clean backupgroup" are intended for totally different
purposes and the only surprise would be if they did what you wanted.

Natural expiration of the data is good option and might save you some tape
drive load if you do "move nodedata" later. But your course of action is
correct and you can do it even right now.

Zlatko Krastev
IT Consultant






Kurt A Rybczyk <rybczyk AT US.IBM DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
25.11.2003 21:51
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        data in wrong stgpool


I recently discoverd that someone setup a copygroup wrong and data was
being sent to the wrong storage pool. My problem is that the stgpool it
was being sent to also has a copystgpool. I did a move nodedata <node>
from=<source> to=<dest> and that ran okay. It moved from one primary pool
to another. Now, I'd like to get the data in the copystgpool removed too.
I've tried expire i and backup stg. I've also tried clean archdir and
clean backupgroup and that hasn't worked. The only other thing I can come
up with is to collocate the offsite pool and do a bunch of move nodedata
to isolate that data on specific offsite volumes, then doing a del v
discard=y on them.

Any thoughts or suggestions would be much appreciated.  Thanks in advance.

kr

----------------------------------------------
Kurt Rybczyk