> Hello,
>
> There was indeed a change in 1.38.x (perhaps as you say 1.38.6). However, it
> applies only if the InChanger flag is set in the Media record, which means
> that in principle we are dealing with an Autochanger, and in that case, I
> believe that the behavior is correct.
>
> There is no way to disable the new behavior except by setting the InChanger
> flag in each Volume to zero.
>
thanks for your answer but I can't say that i really understand the new way
for me the first was the good way : imagine you have a pool big enough to do for example 3 full backup during 3 weeks with a volume retention of 3 weeks, with the first alogrithm when the data remain relatively constant the volumes are recycled normally each 3 weeks, if the amount of data is growing enough (for any reason ) to reach the capacity of the pool before the end of retention period of the oldest volume then bacula will pick a tape in the scratch pool an then continue working from weeks to weeks
with the second algorithm bacula will pick and pick tapes in the
scratch pools to the end of its capacity without checking the retention date of
the normal pool killing the beautifull prevision you make ? this is particularly
critical if the goal is to optimise the utilisation of a minimal number of tapes
in the autochanger in order to anticipate the future growth of datas
is there a thing I misunderstand
---------------------------------
Webmail IUT Bayonne, Pays Basque.
