On Monday 17 April 2006 18:34, Jon LaBadie wrote:
>
> promoting == moving to a lower numeric level
> bumping   == moving to a higher numeric level
>
> If the last dump of a DLE was an incremental, and it is not
> scheduled for a level 0, then amanda must decide to promote,
> repeat, or bump the level.  This decision is based on the
> estimated sizes of each of the three levels and is influenced
> by parameters bump{size|mult|days} (by default 10MB, 1.5/level,
> and 2 days respectively).
>
> For Ross' vtape based backups size was a consideration and he
> wanted rapid, easier promotion (lower all values).  For my ptape
> based backups that was not a problem and I seldom see anything
> higher than level 2.
>
> Independent of the planning for "todays" dumps, amanda also
> considers the longer range schedule.  If the total size of
> the estimated dumps in the above planning is small relative
> to what amanda considers "balanced" (Size of all level 0s
> divided by their respective runspercycle) then amanda may
> promote some DLEs all the way to level 0 hoping to reduce
> the oversized dumps anticipated in the future.  AFAIK only
> one parameter influences this, maxpromotedays, default 10000.
> It is the maximum number of DLEs that can be promoted for
> long range planning.  Set it to zero and nothing will be
> promoted for this purpose.  A setting of 1 or 2 may reduce
> promoting drastically at some sites.
>
Thanks, that does help.  I shall see what I can do with that.  It sounds as 
though it would help.

Anne

pgplIKdxGNgkd.pgp
Description: PGP signature