> On Jul 19, 2016, at 2:18 PM, Stefan G. Weichinger <[email protected]> wrote:
>
> Am 19.07.2016 um 20:56 schrieb Jean-Louis Martineau:
>> Stefan,
>>
>> chg-aggregate fail if one of the changer fail, it is the way it is
>> designed.
>> Both disk must be mounted to works.
>
> I understood that differently from your mail then.
> My use-case would be more of "use one of the changers", yes.
>
>> We could add a property so that it use all the available child changer,
>> eg. fail only if all child fail.
>
> Yes! Sounds great to me.
> And as we are at wishes:
>
> it would be great to have a parameter like:
>
> use_each_changer_for_number_of_X_runs
>
> although I have to think about that.
>
> If the external disks don't get changed (the admin forgets to unplug
> disk1 and plug in disk2) the dumps should not FAIL. It should WARN in
> the report mail but continue to rotate through vtapes on disk1.
>
> Opinions, anyone?
Wouldn’t that just be a change in the RUNTAPES parameter?
It will start re-using only after it exceeds that parameter. BUT if you have
more tapes available than
that parameter, it uses all of them before beginning to re-use. (At least,
with real tapes.)
So if I want it CAPABLE of re-using tapes, I have to set the RUNTAPES param to
the value of the minimum
I insist it keeps before overwriting. I have always been able to have MORE
than that number of tapes, and
it will use them all before re-writing, if they are inserted.
Deb Baddorf
>
>> For testing, you can try to remove all
>> if (grep { defined($_->[0]) } @$kid_results) {
>> ...
>> }
>> block of code
>
> ... in /usr/lib/perl5/vendor_perl/5.20.2/Amanda/Changer/aggregate.pm, right?
>
> Thanks, I will test asap (=tomorrow)
>
>
