Re: Group collocation

I'm scheduling the following scripts to automatically assign new nodes to a 
copy group.

Utilities available with TSM 5.3 server when dealing with collocation groups.

http://www-1.ibm.com/support/docview.wss?rs=100&q1=collocate+group&uid=swg21205433&loc=en_US&cs=utf-8&lang=en

john underdown
junderdown AT sti.synovus DOT com

>>> LISTSERV AT VM.MARIST DOT EDU 10/15/05 4:35 AM >>>

------------------------------

Date:    Fri, 14 Oct 2005 08:42:21 -0500
From:    fred johanson <fred AT UCHICAGO DOT EDU>
Subject: Re: Group collocation

I agree.  It's just another instance of eternal vigilance forced on us by=20
TSM.  I have a group adding a dozen or more new clients a day.  If I don't=
=20
get them assigned to groups and they push so much to disk to force a=20
migration, I wind up with a dozen or so 3592 cartridges with less than 1%=
 used.

More important, until a fix is released, is that MIGDELAY be set to 0 for=20
any disk that goes to a group collocated tape.  Unhappy things occur=20
otherwise.  And I am still working with Level II whether there are=20
additional problems if you go from FILE to group collocated tape.


At 10:15 PM 10/13/2005 -0500, you wrote:
>I know about this because I got bitten by it. I realize it's working as=20
>designed, but I think the design bites. Intuition tells me that if you=20
>collocate by group, any node not in a group doesn't get collocated. But=20
>that's not the way it is.
>
>--
>Mark Stapleton (stapleton AT berbee DOT com)
>IBM Certified Advanced Deployment Professional
>  Tivoli Storage Management Solutions 2005
>IBM Certified Advanced Technical Expert (CATE) AIX
>Berbee Information Networks
>Office 262.521.5627
>
>
>
> >-----Original Message-----
> >From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> >Behalf Of Kolbeinn J=F3sepsson
> >Sent: Thursday, October 13, 2005 9:22 PM
> >To: ADSM-L AT VM.MARIST DOT EDU 
> >Subject: Re: Group collocation
> >
> >My apologizes, Mark you are correct!
> >
> >The best practise should be to use at least two seperate
> >storagepools, the
> >first with collocation=3Dno (where all non-collocated nodes
> >belongs to) and
> >the second with collocation=3Dgroup (where nodes in collocaton groups
> >belongs), you can then chose if you use the second pool also for
> >collocation by node (non grouped nodes) or if you add the
> >third stgpool
> >with collocation=3Dnode (and perhaps the fourth stgpool with
> >collocation=3Dfilespace if your environment is "large enough").
> >
> >Best regards,
> >Kolbeinn
> >
> >
> >
> >
> >"Stapleton, Mark" <mark.stapleton AT BERBEE DOT COM>
> >Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> >14.10.2005 01:39
> >Please respond to
> >"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> >
> >
> >To
> >ADSM-L AT VM.MARIST DOT EDU 
> >cc
> >
> >Subject
> >Re: Group collocation
> >
> >
> >Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
> >>If I take a storage pool and change it to GROUP from NO
> >>collocation, what
> >>about the data for nodes that ARE NOT in collocation groups ?
> >>Does their
> >>data get collocated or not ?  Will I all of a hsudden go from
> >1-2 daily
> >>LTO2 mounts to 30 ?
> >
> >From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> >Behalf Of Kolbeinn J=F3sepsson
> >>Only data from nodes in collocationgroup will be collocated, data from
> >>other nodes in same stgpool will not be collocated.
> >
> >This is incorrect. My experience has been that, when setting a pool to
> >"collocation by group", that any node not belonging to a
> >collocation group
> >will get its data to that pool collocated.
> >
> >(from page 312 of the TSM 5.3 for Windows Administrators' Reference)
> >=3D=3D=3D=3D
> >GRoup
> >Specifies that collocation is enabled at the group level for
> >client nodes.
> >The server attempts to put data for nodes that belong to the same
> >collocation group on as few volumes as possible. If the nodes in the
> >collocation group have multiple file spaces, the server does
> >not attempt
> >to collocate those file spaces.
> >
> >If you specify COLLOCATE=3DGROUP but do not define any groups, data is
> >collocated by node. Similarly, if you specify COLLOCATE=3DGROUP and you
> >define a group but do not add nodes to the group, data is
> >collocated by
> >node.
> >=3D=3D=3D
> >
> >The workaround I found is to create collocation groups and
> >populate them,
> >then create one more collocation group that contains all other
> >nodes that
> >write to that storage pool that are *not* already in a group.
> >
> >--
> >Mark Stapleton (stapleton AT berbee DOT com)
> >IBM Certified Advanced Deployment Professional
> > Tivoli Storage Management Solutions 2005
> >IBM Certified Advanced Technical Expert (CATE) AIX
> >Berbee Information Networks
> >Office 262.521.5627
> >
> >
> >



-----------------------------------------
NOTICE: This communication is intended only for the person or entity to
whom it is addressed and may contain confidential, proprietary, and/or
privileged material. Unless you are the intended addressee, any review,
reliance, dissemination, distribution, copying or use whatsoever of
this communication is strictly prohibited. If you received this in
error, please reply immediately and delete the material from all
computers. Email sent through the Internet is not secure. Do not use
email to send us confidential information such as credit card numbers,
PIN numbers, passwords, Social Security Numbers, Account numbers, or
other important and confidential information.