On Mar 13, 2006, at 5:55 PM, Remco Post wrote:

So now for the question at hand, how do aggregation and the maxsize
parameter interact? Both during B/A and migration/reclamation?

Remco -

There's no mystery in this - it's all laid out in the IBM
documentation, as previously indicated. During backup, client data is
formed into a transaction according to the limits imposed by the TXN*
parameters, and if the determined size fits in the primary landing
area, it goes there, else further down in the stgpool hierarchy.
Migration can happen if the current size of an Aggregate fits in the
next lower stgpool.

Your desire to service restorals without tape argues for an
investment in some kind of disk array, with a Migdelay value such
that older data migrates to tape.

   a weary Richard Sims