Content preview:  Hi Jennifer, While there is a COLLOCGROUP option to MOVE 
NODEDATA,
    it sounds like you just want to move one node's data. Any kind of data 
movement
    operation will try to respect the collocation setting you provide at the
   node level, assuming you have the storage pool set to collocate by group as
    well. Something like this would move the node's data to fresh tapes in the
    same storage pool: [...]

 Content analysis details:   (0.7 points, 5.0 required)

  pts rule name              description
 ---- ---------------------- --------------------------------------------------
  0.7 SPF_NEUTRAL            SPF: sender does not match SPF record (neutral)
 -0.0 RP_MATCHES_RCVD        Envelope sender domain matches handover relay 
domain
X-Barracuda-Connect: mx.gs.washington.edu[128.208.8.134]
X-Barracuda-Start-Time: 1510243908
X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384
X-Barracuda-URL: https://148.100.49.28:443/cgi-mod/mark.cgi
X-Barracuda-Scan-Msg-Size: 3707
X-Virus-Scanned: by bsmtpd at marist.edu
X-Barracuda-BRTS-Status: 1
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=3.5 
QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.5 tests=
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.44667
        Rule breakdown below
         pts rule name              description
        ---- ---------------------- 
--------------------------------------------------

Hi Jennifer,

While there is a COLLOCGROUP option to MOVE NODEDATA, it sounds like you
just want to move one node's data.  Any kind of data movement operation
will try to respect the collocation setting you provide at the node level,
assuming you have the storage pool set to collocate by group as well.
Something like this would move the node's data to fresh tapes in the same
storage pool:

MOVE NODEDATA some_node FROMSTGPOOL=some_pool

As Marc said, though, as long as collocation at the pool level is set to
either NODE or GROUP, there is no difference between a node being in no
collocation group, and a node being in a collocation group that has no
other nodes.

As for starting a full backup, the TSM terminology is somewhat confusingly
"selective backup". I'm not sure if this will start a VSS backup but it
will backup all the eligible files in your backup domain.

On Thu, Nov 09, 2017 at 03:57:43PM +0000, Drammeh, Jennifer C wrote:
> Marc,
>
>    I removed the node from the collocation group and added it to the new 
> collocation group - where it resides by itself. Will the move nodedata 
> command move the data from the tapes in the old collocation group to tapes in 
> the new collocation group? Also, do you know how to initiate a FULL new 
> backup of the entire system.
>
>
> Thanks!
>
>
> Jennifer
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of Marc Lanteigne
> Sent: Friday, November 03, 2017 3:07 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Question on Collocation
>
> Hi Jennifer,
>
> The backup always only applies to the filesystem backup, not systemstate. 
> You???ll have to change the mode of the systemstate backup to get a full.
>
> Or use move nodedata to move it all together.
>
> BTW, you would just have needed to remove the node from the collocation 
> group. Nodes not in a collocation group are collocated by node.
>
> Marc...
>
> Sent from my iPhone using IBM Verse
>
> On Nov 3, 2017, 6:11:07 PM, jdrammeh AT U.WASHINGTON DOT EDU wrote:
>
> From: jdrammeh AT U.WASHINGTON DOT EDU
> To: ADSM-L AT VM.MARIST DOT EDU
> Cc:
> Date: Nov 3, 2017, 6:11:07 PM
> Subject: [ADSM-L] Question on Collocation
>
>
>  I use collocation and I have a node where the System Admin has requested 
> that his data from a particular node be isolated on tapes by itself. I 
> created a collocation group and have associated this one node with the new 
> group. This node had previously been backing up to a different collocation 
> group. I created a new Policy Domain and associated the node with it as well. 
> This policy domain is set to send the data direct to tape instead of going to 
> our diskpool. I also modified the settings on the server to allow this system 
> to have 2 mount points.
>  I had the SA launch a "full" manual backup from the GUI - using the "Always 
> Backup" option. Here are the problems I am seeing.
>  1.       I can see that the system state data when to a tape that was 
> already used by other nodes (which tells me the collocation is not working)
>  2.       It only mounted 1 tape in a drive while performing the backup
>  3.       The metrics at the end showed that it inspected 283 GB of data and 
> only transferred 175 GB which means it did not actually perform a full backup.
>  Any ideas to help get a FULL backup of this data alone on a single 1 or 2 
> tapes and ideally using multiple tape drives to speed things up? (for backup 
> and restore)  Thanks!
>  Jennifer

--
-- Skylar Thompson (skylar2 AT u.washington DOT edu)
-- Genome Sciences Department, System Administrator
-- Foege Building S046, (206)-685-7354
-- University of Washington School of Medicine