Re: [ADSM-L] Help on q nodedata

It looks like the strange behavior is in MOVE NODEDATA, not Q NODEDATA.
You should believe what Q NODEDATA says. Something went wrong with the
move - even though it says SUCCESS. Do something like

Q ACTLOG BEGINT=xx:xx BEGIND=xx/xx/2013 SEARCH='MOVE NODEDATA'

to see why it stopped and thought it had succeeded before moving all of
the data. Perhaps a restore or reclamation underway? Beware that it
likely has to un-dedup the data as a part of the MOVE NODEDATA process.

Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT edu
======I have not lost my mind -- it is backed up on tape somewhere.=====



On Thu, 31 Oct 2013, Robert Ouzen wrote:

>Hi to all
>
>I have a strange behavior on a client running the Q NODEDATA EDUNW  , here the 
>output:
>
>
>
>Node Name            Volume Name                        Storage Pool         
>Physical
>                                                        Name                  
> Space
>                                                                             
> Occupied
>                                                                               
> (MB)
>----------------     ------------------------------     ----------------     
>--------
>EDUNW                T:\DEDUP6\00053C08.BFS             DEDUP6TSM             
>18.16
>EDUNW                T:\DEDUP6\00053C21.BFS             DEDUP6TSM             
>71.95
>EDUNW                T:\DEDUP6\00053C25.BFS             DEDUP6TSM            
>4,964.89
>EDUNW                T:\DEDUP6\00053C39.BFS             DEDUP6TSM              
>0.06
>EDUNW                T:\DEDUP6\00053C44.BFS             DEDUP6TSM             
>699.58
>EDUNW                \\DD580G\BACKUP\POSTBACK\EDUC-     DD_EDUCATION         
>36,533.5
>                      ATION\00000000.BFS                                       
>   7
>EDUNW                \\DD580G\BACKUP\POSTBACK\EDUC-     DD_EDUCATION         
>37,187.1
>                      ATION\00000001.BFS                                       
>   4
>EDUNW                \\DD580G\BACKUP\POSTBACK\EDUC-     DD_EDUCATION         
>38,004.6
>                      ATION\00000002.BFS                                       
>   9
>EDUNW                \\DD580G\BACKUP\POSTBACK\EDUC-     DD_EDUCATION         
>33,756.1
>                      ATION\00000003.BFS                                       
>   9
>EDUNW                \\DD580G\BACKUP\POSTBACK\EDUC-     DD_EDUCATION         
>24,543.9
>                      ATION\00000004.BFS                                       
>   1
>EDUNW                \\DD580G\BACKUP\POSTBACK\EDUC-     DD_EDUCATION         
>32,374.4
>                      ATION\00000005.BFS                                       
>   0
>
>The correct storage to be on is:  DD_EDUCATION
>
>I run several times a move nodedata edunw from=dedup6tsm  to=dd_education   
>recons=yes   with every time success process.
>
>But still  got this output ?
>
>I did to a : q nodedata * vol= T:\DEDUP6\00053C08.BFS             and still 
>see reference of node EDUNW on it ?
>
>tsm: POSTBACK>q nodedata edunw vol=S:\DEDUP6\00053BB2.BFS
>
>Node Name            Volume Name                        Storage Pool         
>Physical
>                                                        Name                  
> Space
>                                                                             
> Occupied
>                                                                               
> (MB)
>----------------     ------------------------------     ----------------     
>--------
>EDUNW                S:\DEDUP6\00053BB2.BFS             DEDUP6TSM             
>57.52
>
>How I can be rid of those entries ?
>
>My Tsm server version is:   6.3.4.200
>My Tsm client version is:     6.2.2.0
>
>T.I.A  Regards
>
>Robert
>