Rick has already brought up MIGRATE STG, which probably is the normal way to do 
this. 

Remember that MOVE NODEDATA can also move data among primary storage pools 
(including back to a random access storage pool, good for when you anticipate 
an important recovery operation). You can even set up collocation groups so 
that your MOVE NODEDATA covers more than one node at a time (even if you don’t 
use collocation by groups in your storage pools.) It might be more work to 
execute than MIGRATE STG, but it gives you control about which data moves 
first, if that’s important to you. 

Nick

On Dec 9, 2013, at 3:31 AM, mik <tsm-forum AT BACKUPCENTRAL DOT COM> wrote:

> I have the response to my question it's impossible.
> 
> Arg thanks for reply inestler i suspected that.
> 
> But now i have more question ^^
> 
> If i create new tapepool named by exemple TAPEPOOL2 with disk, can i migrate 
> the actual diskpool to the new TAPEPOOL2 (disk)
> 
> If it's possible to performe move data AXXXXXX (from tapepool) to 
> stg=TAPEPOOL2 ?
> 
> The goal of that it's to remplace the actual tapepool from tape to tapepool2 
> disk (one of drive are down and the second was tired) it's just a tempory 
> solution to continue to save the data just before to export nodedata to the 
> new TSM server with LTO6 tape library (actually TSM LTO3 with one HS drive 
> and second tired drive)
> 
> Thanks for reply.
> 
> Regards, Mickael
> 
> +----------------------------------------------------------------------
> |This was sent by bobpatrick808182 AT yahoo DOT fr via Backup Central.
> |Forward SPAM to abuse AT backupcentral DOT com.
> +----------------------------------------------------------------------