sounds like something I might want to force, if we used co-location at all.

I am thinking of setting up some smaller disk/tape pools for 'high
visibility'
clients that would need to be restoreed first in case of a disaster.  This
would mean spinning fewer tapes to get those clients restored, while not
having
the luxury of a library large enough to do general co-location.

-----Original Message-----
From: Alex Paschal [mailto:AlexPaschal AT FREIGHTLINER DOT COM]
Sent: Wednesday, May 05, 2004 3:23 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Andy.....What is Imperfect Collocation???


Here's how the server selects tapes in a collocated stgpool.  (From the
Admin Guide)

1. A volume that already contains files from the same client node
2. An empty predefined volume
3. An empty scratch volume
4. A volume with the most available free space among volumes that already
contain data

I think Andy is referring to perfect collocation as a stgpool that never
gets to step 4 because there are enough empty scratch tapes to maintain a
one-node-per-tape situation.  Imperfect collocation would be where
maxscratch limits the scratch tapes in order to get multiple nodes "stacked"
on one tape.

I don't know why you'd run out of stgpool space in a collocated stgpool
unless all of your tapes are full _and_ you're running into maxscratch.

Thanks,
Alex Paschal
Freightliner, LLC
(503) 745-6850 phone/vmail


-----Original Message-----
From: David Nicholson [mailto:David_R_Nicholson AT WHIRLPOOL DOT COM]
Sent: Wednesday, May 05, 2004 5:33 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Andy.....What is Imperfect Collocation???


"Imperfect Collocation"???   My experience has been that when I reach the
maxscratch threshold the storage group is full and cant accept data. Am I
missing something??



Dave Nicholson
Whirlpool Corporation





Andrew Raibeck <storman AT US.IBM DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
05/04/2004 07:09 PM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: What ever happened to Group Collocation ?


Zoltan,

I don't know what you were specifically told about the new feature, but
keep in mind that any such disclosures are usually with the caveats
"subject to change".   :-)

To the best of my knowledge this is currently targeted for our next major
release this fall. (Caveat: This statement does not represent a formal
announcement or commitment, and is subject to change.)

As others have suggested, check the tape utilization for your smaller
nodes and consider using imperfect collocation (reduce MAXSCRATCH which
will allow multiple nodes to share a tape).

Some other thoughts:

- Make sure your tapes are available to the server for additional writes,
i.e. not in read-only or other access state that prevents appending data
to the tape.

- Check the status of the tapes to make sure they aren't full. If they are
full, then maybe you need to run reclamation?

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.



Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
05/04/2004 13:13
Please respond to
"ADSM: Dist Stor Manager"


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: What ever happened to Group Collocation ?






I have already thought of this idea. I was hoping for GROUP COLLOCATION.

The problem with this idea/design is I have to essential duplicate
*EVERYTHING*, such as admin processes, operator training, etc.  Also, this
means I have to set aside disk storage (which is very limited on my zOS
system) to dedicate for each pool, that can't be shared, and hope I don't
guess wrong on how much each pool/group needs.

Thanks for the suggestions.  Unfortunately, this is probably the way I
will have to go.

One confusion is why do I have sooooo many partially filled tapes ?   I
don't have this many nodes ?