If you want to pursue this, you'll have to run a select statement against the VOLUMEUSAGE to find the relevant offsite pool volumes. Check in the volumes from the resultant list, and run your MOVE NODEDATA.
-- Mark Stapleton >-----Original Message----- >From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On >Behalf Of Rushforth, Tim >Sent: Wednesday, June 09, 2004 9:39 AM >To: [EMAIL PROTECTED] >Subject: Re: Primary Pool and Copypool Relationship > >OK, #1 below wouldn't work either without bringing offsite tapes back! > >>Yes. Keep in mind that MOVE NODEDATA is not very useful for offsite >>copypools, since it requires the copypool-volumes to be onsite and >>available. (It doesn't work like e.g. MOVE DATA does, which >gets the files >>from the primary pool) >>-- >>Jurjen Oskam > >-----Original Message----- >From: Rushforth, Tim >Sent: June 7, 2004 3:05 PM >To: 'ADSM: Dist Stor Manager' >Subject: RE: Primary Pool and Copypool Relationship > >Ooops forgot about that restriction. To do this without bringing back >offsite tapes or deleting all copy pool data for some nodes >temporarily: > >1. Move nodedata from Copy Pool #1 to Copy Pool #1 (to new >volumes) for the >nodes you want to move. >2. Move nodedata Primary Pool #1 to Primary Pool #2 >3. Backup primary pool #2 to Copy Pool #2 >4. Delete the new volumes from 1. > > >-----Original Message----- >From: Stapleton, Mark [mailto:[EMAIL PROTECTED] >Sent: June 7, 2004 2:54 PM >To: [EMAIL PROTECTED] >Subject: Re: Primary Pool and Copypool Relationship > >From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On >Behalf Of >Rushforth, Tim >>I guess the proper sequence should have been: >> >>1. Move nodedata from Copy Pool #1 to Copy Pool #2 (this way TSM will >use >>the data on Primary Pool #1 as the source data) >>2. Move nodedata from Primary Pool #1 to Primary Pool #2 > >Unfortunately, step #1 is not possible. MOVE NODEDATA supports data >moves within a single copy pool, but not between two copy pools. > >-- >Mark Stapleton > >