ADSM-L

Re: [ADSM-L] Move NodeData

2012-04-02 12:10:21
Subject: Re: [ADSM-L] Move NodeData
From: George Huebschman <george.huebschman AT GMAIL DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 2 Apr 2012 12:05:30 -0400
I see that you are correct.  I also see the answer to my question...a few
lines from where I quoted.  I should have read more attentively:
" This operation will not move data on volumes with access modes of offsite,
unavailable, or destroyed."

On Mon, Apr 2, 2012 at 10:49 AM, Ehresman,David E.
<deehre01 AT louisville DOT edu>wrote:

> You CAN use Move Data on copy storagepools but only to move to other
> volumes in the SAME storagepool.  You cannot Move Data copy storagepool
> data to a different storagepool.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> George Huebschman
> Sent: Monday, April 02, 2012 10:20 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Move NodeData
>
> David,
> TSM says you can use it for copy pool data:
> 3.35.5 MOVE NODEDATA (Move data by node in a sequential access storage
>       pool)
>
> Use this command to move data located in a sequential-access storage
> pool. You can move data for one or more nodes or for a group of
> collocated nodes. You can also move selected file spaces for a single
> node. The data can be located in a primary storage pool, a copy storage
> pool, or an active-data pool.
>
>
> On Mon, Apr 2, 2012 at 9:12 AM, Ehresman,David E.
> <deehre01 AT louisville DOT edu>wrote:
>
> > The stgpool parameter on Move Data is only valid for primary storage pool
> > volumes.  You cannot use the Move Data command to move copypool data from
> > one storagepool to a different one.
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On 
> > Behalf Of
> > George Huebschman
> > Sent: Friday, March 30, 2012 2:30 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: [ADSM-L] Move NodeData
> >
> > I think I have misunderstood how the command "move nodedata" works in
> > regard to offsite media.
> > I had believed that it functioned in the same way that reclamation and
> move
> > data operations worked, utilizing onsite media to write new offsite
> media.
> >
> > This quote relates to  the "move data" command:
> > You can use this command to move files from an offsite volume in a copy
> > storage pool or active-data pool. Because the offsite volume cannot be
> > mounted, the server obtains the files that are on the offsite volume
> > from either a primary storage pool, another copy storage pool, or
> > another active-data pool. These files are then written to the
> > destination volumes in the original copy storage pool or active-data
> > pool.
> >
> > I see nothing like that in the description of the "move nodedata"
> command.
> > It looks like I made a false assumption.
> > Is that so?
> > --
> > George Huebschman
> > Cell 301 875-1227
> >
> > "When you have a choice, spend money where you would prefer to work if
> you
> > had NO choice."
> >
>
>
>
> --
> George Huebschman
> Cell 410 522-8581
>
> "When you have a choice, spend money where you would prefer to work if you
> had NO choice."
>



--
George Huebschman
Cell (301) 875-1227


"When you have a choice, spend money where you would prefer to work if you
had NO choice."

<Prev in Thread] Current Thread [Next in Thread>