move nodedata looks  like it allows you to move a nodes data from one
storage pool to another.  Say  for instance, you knew you had a big
restore coming up, and had the time, you could move that nodes data into
the disk pool.  The downside that  was brought up is that it copies both
active and inactive data, so you could potentially be copying much more
data than you need for the restore.

Andy Carlson                             |\      _,,,---,,_
andyc AT andyc.carenet DOT org            ZZZzz /,`.-'`'    -.  ;-;;,_
BJC Health System                       |,4-  ) )-,_. ,\ (  `'-'
St. Louis, Missouri                    '---''(_/--'  `-'\_)
Cat Pics: http://andyc.dyndns.org/animal.html

On Tue, 12 Mar 2002, Joseph Dawes wrote:

> what is move nodedata?
>
>
>
>                     Andy Carlson
>                     <andyc AT ANDYC DOT CA       To:     ADSM-L AT VM.MARIST 
> DOT EDU
>                     RENET.ORG>            cc:
>                     Sent by: "ADSM:       Subject:     Re: TSM 5.1
>                     Dist Stor
>                     Manager"
>                     <ADSM-L AT VM DOT MARI
>                     ST.EDU>
>
>
>                     03/12/02 02:07
>                     PM
>                     Please respond
>                     to "ADSM: Dist
>                     Stor Manager"
>
>
>
>
>
>
> #2 is not the panacea that it sounds like.  The dual writes to the
> copypool's happens during session data transfer to disk pool - thus, you
> must have a tape drive per session doing the dual write.
>
> Andy Carlson                             |\      _,,,---,,_
> andyc AT andyc.carenet DOT org            ZZZzz /,`.-'`'    -.  ;-;;,_
> BJC Health System                       |,4-  ) )-,_. ,\ (  `'-'
> St. Louis, Missouri                    '---''(_/--'  `-'\_)
> Cat Pics: http://andyc.dyndns.org/animal.html
>
> On Tue, 12 Mar 2002, Richard L. Rhodes wrote:
>
> > We had a meeting with IBM last week where they described some of the
> > new features of 5.1 - coming within a few weeks.
> >
> > 1)  multi session restore
> > 2)  simultaneous writes to copy pools (more than one)
> > 3)  a "move nodedata" command
> > 4)  lan-free backup/restore (I thought it already had this)
> > 5)  hpux lan-free
> >
>