On Tue, Nov 11, 2003 at 01:06:31PM -0500, Lee, Gary D. wrote: > Don't think you can do a move nodedata for a copy pool. Must be done > on a primary pool.
From: Jurjen Oskam [mailto:[EMAIL PROTECTED] >That's not true. MOVE NODEDATA works on any storagepool, *if* the needed volumes are onsite and >readable. Ahem. From HELP MOVE NODEDATA from TSM server version 5.1.6.2: "...if the source storage pool is a copy storage pool the destination must be the same copy storage pool." However, this may all really be moot. If the old copy pool was up-to-date, and the new copy pool is up-to-date, the data in the old copy pool is redundant. In *that* case, there's no need to run a MOVE NODEDATA, since all data is already in the new pool. You can safely run DEL VOLUME <VOLUME> DISCARDDATA=YES for each volume in the old copy pool, and if those volumes were all listed as ACCESS=OFFSITE, you must follow up with UPD VOL * WHERESTGPOOL=<OLDCOPYPOOL> ACCESS=READWRITE at which time all the volumes in the old copy pool will disappear. -- Mark Stapleton ([EMAIL PROTECTED])
