On Wed, Nov 17, 2010 at 08:24:51AM -0500, Richard Sims wrote:
> The line with the "Changed" tells the story.  Remember that TSM client-server 
> interactions are *transaction* based, not file-by-file.  If a constituent 
> element of the transaction changes, the transaction is void and has to be 
> repeated, according to your Changingretries choice.  This relates to 
> Aggregate-based storage in the TSM server.

Yes, I expected that much...

But it is just a waste of bandwidth to send the whole aggregate again because
maybe one (somteimes small) file in it has been changed. I saw a lot
of such retries so am worried about it a bit. I sure this can be implemented
in a miuch more optimal way.

-Marcel
--
     ======--------         Marcel J.E. Mol                MESA Consulting B.V.
    =======---------        ph. +31-(0)6-54724868          P.O. Box 112
    =======---------        marcel AT mesa DOT nl                 2630 AC  
Nootdorp
__==== www.mesa.nl ---____U_n_i_x______I_n_t_e_r_n_e_t____ The Netherlands ____
 They couldn't think of a number,           Linux user 1148  --  counter.li.org
    so they gave me a name!  -- Rupert Hine  --  www.ruperthine.com