Hi Silvio,
it looks like we missed some places in the documentation when we
deprecated those options. Just to clarify: We only deprecated the
`Fd->Client` and `Sd->Storage` options. We did not deprecate the
`Sd->Device` option.
The idea is that previously you could e.g. define
`MaximumConcurrentJobs` both in `Dir->Storage` and `Sd->Storage` and it
would basically always take the minimum of the two for the actual
`MaximumConcurrentJobs` value. This basically meant that you had to
keep both those values in sync or you would get unexpected results.
In an effort to make our configuration less confusing we decided to set
the `Sd->Storage` and `Fd->Client` options to 10000, so that you only
ever need to configure it on the director.
We plan to remove these deprecated options completely sooner or later
unless we find a good reason to not do so.
To answer your question: If you set `MaximumConcurrentJobs`
(Dir->Storage) to some value, then the storage daemon will run up to
that many jobs in parallel.
If you want multiple jobs to be able to write to the same device at the
same time, you can set `MaximumConcurrentJobs` (Sd->Device) -- this
option is not deprecated.
Take the warning at
https://docs.bareos.org/Configuration/StorageDaemon.html#config-Sd_Device_MaximumConcurrentJobs
into account though. For most device types its better to define
multiple of them, each only allowing up to one job, instead of just one
allowing multiple jobs at the same time.
I hope this clears some things up!
Kind Regards
Sebastian Sura
Am 16.12.24 um 08:41 schrieb Silvio Schloeffel:
Thanks Sebastian,
Yes, you're right, I was looking in the wrong place. Sorry for the
confusion.
What surprises me is that the option is marked as deprecated for both
the client and the storage daemon.
However, the documentation still lists this option for the storage
daemon and multiple storage devices for disc based backups.
https://docs.bareos.org/TasksAndConcepts/VolumeManagement.html#concurrentdiskjobs
So if I disable this option, can I only write to one device at a time?
This would mean that parallel backups from different systems would no
longer work or long-running backups would block other backups.
Best
Silvio
Am 16.12.24 um 06:44 schrieb Sebastian Sura:
Hi Silvio,
you might be looking at the wrong option. https://docs.bareos.org/
Configuration/FileDaemon.html#config-Fd_Client_MaximumConcurrentJobs
is marked as deprecated. Regarding "use this instead": Use the
options in the director instead, i.e.
https://docs.bareos.org/Configuration/
Director.html#config-Dir_Client_MaximumConcurrentJobs
Its definitely a good idea to mention & exlpain this in the client/
storage documentation. Ill create a task for this. Thanks for your
report.
Kind Regards,
Sebastian Sura
Am 13.12.24 um 16:38 schrieb Silvio Schloeffel:
Hi,
after the upgrade I received this message:
using deprecated keyword MaximumConcurrentJobs on line 3 of file
/etc/ bareos/bareos-fd.d/client/myself.conf
It is only a warning so I checked the documentation for a
replacement info:
https://docs.bareos.org/Configuration/Director.html#storage-resource
and found nothing regarding deprecated or "use this instead".
Will the documentation for this keyword be changed or is it just an
indication that something will be changed in the distant future?
Best
Silvio
--
Sebastian Sura [email protected]
Bareos GmbH & Co. KG Phone: +49 221 630693-0
https://www.bareos.com
Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: Stephan Dühr, Jörg 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 visit
https://groups.google.com/d/msgid/bareos-users/32f1ce76-e997-454e-b4d5-1cbb5af9b49f%40bareos.com.
