I wanted to do something similar a while back, and took the time to trace 
the code of the director; the problem is that the director allocates a 
storage instance (a drive, basically) very early on in the job history and 
there is no mechanism to change it. So selecting "the next available drive" 
is not currently possible. I believe/hope it is something the bareos devs 
will change, as doing so will open up a lot more possibilities.

For anyone with some available cash, sponsoring feature development on this 
would be one way to make faster progress. I believe bareos have set up a 
scheme whereby more than one person can contribute to a feature.

On Tuesday, 20 July 2021 at 10:14:16 UTC+1 [email protected] wrote:

> > IMHO bareos should
> > * either not load such configuration, instead of happily taking a list
> > of storages and silently only ever using the first
>
> But this is a valid point and should be changed in Bareos.
>
> Andreas Rogge schrieb am Freitag, 30. April 2021 um 18:52:50 UTC+2:
>
>> Am 28.04.21 um 23:33 schrieb Florian Panzer - PLUSTECH GmbH: 
>> > Yes, that is what I understood from the docs. 
>> > This looks like a "not-yet-implemented" function, or maybe even a bug 
>> > that hasn't been fixed. 
>> The documentation states: 
>> """Be aware that you theoretically can give a list of storages here but 
>> only the first item from the list is actually used for backup and 
>> restore jobs.""" 
>>
>> While I agree that there's room for improvement, there are lots of 
>> issues to address when backing up to multiple storages - I really don't 
>> want to go into more detail here. In the end you'll be better off with 
>> separate pools per storage. 
>>
>> > IMHO bareos should 
>> > * either not load such configuration, instead of happily taking a list 
>> > of storages and silently only ever using the first 
>> > * or use any of the storage (e.g. fallback if the first storage is 
>> full). 
>> A storage is never "full" from Bareos' point-of-view. So this is 
>> currently more or less impossible to implement. 
>> However, if you can come up with a working solution, feel free to open a 
>> pull request. 
>>
>> Best Regards, 
>> Andreas 
>>
>> -- 
>> Andreas Rogge [email protected] 
>> Bareos GmbH & Co. KG Phone: +49 221-630693-86 <+49%20221%2063069386> 
>> http://www.bareos.com 
>>
>> Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 
>> Komplementär: Bareos Verwaltungs-GmbH 
>> Geschäftsführer: S. Dühr, M. Außendorf, J. Steffens, Philipp Storz 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/65f2e7f8-bdea-49e2-925a-6a632c1ffaa6n%40googlegroups.com.

Reply via email to