what i've done in the pass is to make sure there no processing going on in the 
copy pool, flag all filling volumes as read only, and then do a move data for 
the node on the copy pool. the data will be moved to new volumes where it can 
be deleted. u can create a collocgroup to do mutliple nodes at the same time.

update vol * acc=reado wherestg=copypool wherest=fil
move nodedata  node_name from=copypool
or 
move nodedate COLLOCGroup = group_name from=copypool
 
>>> Thomas Denier <Thomas.Denier AT JEFFERSONHOSPITAL DOT ORG> 05/16/07 1:59 PM 
>>> >>> 
----- Dave Mussulman wrote: -----

>Is there a best practice for moving nodes between domains, when
>the domains have different storage pools, copy pools, management
>classes, etc.?  I noticed when I changed nodes to the new domain,
>the new management classes and rebinding occurred (which is fine,)
>but any data stored in the previous storage groups still remains,
>along with its copypool copies. I didn't really expect pre- existing
>data to magically migrate, and since I was taking the old domain's
>primary disk storage pool out of service anyway, I did a 'move data'
>for those old disk volumes to a different tape pool, and then
>removed the disk volumes.
>
>I expected that the next expire inventory would remove the copies
>for the files no longer in the stgpool they were copied from (or
>even that the stgpool no longer existed,) but that didn't happen.
>(I guess the copies are tied to the file without any regard for
>the stgpool they are/were in.) The new domain doesn't have any
>copypools configured, and I'd like to free those copy tapes up.
>How do I do that?

If you want to get rid of all the files in the old copy pool, you
can use 'delete volume' commands with 'discard=yes' to delete the
volumes.

If there is still some data you want to keep in the old copy pool,
you can use the 'delete volume' command and then execute 'backup
stgpool' commands to recopy the data you want to keep.

You mention that the new domain will not have copy pool coverage.
Most TSM administrators consider this a bad idea (unless there is
some kind of protection against media failure built into the tape
infrastructure).

-----------------------------------------
NOTICE: This communication is intended only for the person or
entity to whom it is addressed and may contain confidential,
proprietary, and/or privileged material. Unless you are the
intended addressee, any review, reliance, dissemination,
distribution, copying or use whatsoever of this communication is
strictly prohibited. If you received this in error, please reply
immediately and delete the material from all computers. Email sent
through the Internet is not secure. Do not use email to send us
confidential information such as credit card numbers, PIN numbers,
passwords, Social Security Numbers, Account numbers, or other
important and confidential information.