Thank you.
Actually I set Maximum Concurrent Jobs = 10 in
/etc/bareos/bareos-dir.d/storage/File.conf and it works.
My actual /etc/bareos/bareos-dir.d/storage/File.conf looks currently
like this:
Storage {
Name = File
Address = diufnas26 # N.B. Use a fully qualified name
here (do not use "localhost" here).
Password = "xxx"
Device = FileStorage
Maximum Concurrent Jobs = 10
Media Type = File
}
So I'm working without data spool and just one storage:
/etc/bareos/bareos-sd.d/device/FileStorage.conf
Device {
Name = FileStorage
Media Type = File
Archive Device = /export/backup
LabelMedia = yes; # lets Bareos label unlabeled media
Random Access = yes;
AutomaticMount = yes; # when device opened, read it
RemovableMedia = no;
AlwaysOpen = no;
Description = "File device. A connecting Director must have the same
Name and MediaType."
}
~
"You need to set up multiple devices. Bareos still treats disk volumes
like tape volumes that are appended linearly. Having multiple devices
will allow multiple volumes to be open and appended to while operating."
--> if I understand correctly this statement, this is just necessary if
one will speed up the backup but it's not a must for the concurrent jobs?
What will happen if I add now some more storages in the same repository
/export/backup? (we are already in production).
Regards,
Birgit
On 24/10/19 21:49, Brock Palen wrote:
It works, this person has a nice writeup:
https://www.svennd.be/concurrent-jobs-in-bareos-with-disk-storage/
You need to set up multiple devices. Bareos still treats disk volumes like
tape volumes that are appended linearly. Having multiple devices will allow
multiple volumes to be open and appended to while operating.
BTW set your Concurrent on your director to not be more than your number of
devices as general rule.
Also if you have not I would look at data spooling:
https://docs.bareos.org/TasksAndConcepts/DataSpooling.html
It helps some keeping volumes clean from failed jobs etc. Personally we have
a small SSD pool we spool to then have disk volumes on bulk SATA and Tape. The
SSD deals with data coming in slowly from clients, but then can feed the lower
cost devices optimally for great performance without causing extra wear.
Brock Palen
1 (989) 277-6075
[email protected]
www.mlds-networks.com
Websites, Linux, Hosting, Joomla, Consulting
On Oct 24, 2019, at 4:50 AM, 'DUCARROZ Birgit' via bareos-users
<[email protected]> wrote:
Hi list,
I have a big disk storage and would like run different jobs from different
clients at the same time on this ONE storage, let's say /export/backup.
The "Maximum Concurrent Jobs" is activated in the following files but my jobs
are not running simultaneously:
/etc/bareos/bareos-sd.d/storage/bareos-sd.conf: Maximum Concurrent Jobs = 20
/etc/bareos/bareos-dir.d/director/bareos-dir.conf: Maximum Concurrent Jobs = 10
/etc/bareos/bareos-fd.d/client/myself.conf: Maximum Concurrent Jobs = 20
Which files am I missing?
I'm trying to understand the doc
https://docs.bareos.org/TasksAndConcepts/VolumeManagement.html#concurrentdiskjobs
but actually it's not clear to me in which file I must use
Maximum Concurrent Jobs = 4
then
Maximum Concurrent Jobs = 20
then
Maximum Concurrent Jobs = 1
??
and also if it is possible to just use ONE FileStorage
Any help is really appreciated!
Regards,
Birgit
--
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/02c23952-0053-59fc-b1a5-03abeb9a9598%40unifr.ch.
--
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/ec2ef106-f958-1334-397b-d4c0508216ba%40unifr.ch.
