Our solution is to have our large clients in a colocated storage pool,
and our smaller clients are grouped into several non colocated pools.
This way, the larger clients each get their own tape, and the smaller
clients share.

Kenton Maguire wrote:
>
> We are backing up some of our larger system to a storage pool that is
> utilizing collocation with hopes of reducing the number of tape mounts
> required for complete recovery,  i.e. disaster.  While this model works
> well, it does consume a tremendous amount of scratch tapes in our 3575 tape
> library.
>
> Is there any method that would allow us to reduce and/or control the number
> of clients stored on each tape rather than dedicating a tape to each
> client?  I've been told that by reducing the number of 'max scratch' tapes
> for the storage pool, it would force ADSM to 'stack' client data.  However,
> I haven't seen any documentation describing this method.