Re: [Bacula-users] Again LTO9 and performances...

2024-06-11 Thread Bill Arlofski via Bacula-users

On 6/11/24 10:45 AM, Marco Gaiarin wrote:


Sorry, i really don't understand and i need feedback...

I've read many time that tapes are handled better as they are, sequential
media; so they need on storage:

Maximum Concurrent Jobs = 1


Hello Marco,

If you are using DataSpooling for all of your jobs, this setting is somewhat redundant because Bacula will de-spool exactly 
one Job's Data Spool file at a time.


With DataSpooling enabled in all jobs, the only "interleaving" that you will have on your tapes is one big block of Job 1's 
de-spooled data, then maybe another Job 1 block, or a Job 2 block, or a Job 3 block, and so on, depending on which Job's 
DataSpool file reached the defined maximum Job Spool size at particular times throughout the backup window, or when one hits 
the total MaximumSpool size and begins de-spooling.


If, on the other hand, you have many clients and enough network bandwidth, you can disable Data Spooling, and increase the 
Ta

pe Drive's MaximumConcurrentJobs setting and Bacula will stream and interleave 
the data from all the concurrently running jobs.

But, you can probably never really guarantee that all jobs will be streaming enough data concurrently to saturate the link to 
the Tape Drive, so using DataSpooling to *fast*, local, SSD, flash, or NVMe etc drives is probably a better and more 
consistent solution.



Hope this helps!
Bill

--
Bill Arlofski
w...@protonmail.com



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Again LTO9 and performances...

2024-06-11 Thread Marco Gaiarin


>> Not for a single job. When the storage daemon is writing a job's spooled 
>> data to tape, the client must wait. However, if multiple jobs are 
>> running in parallel, then the other jobs will continue to spool their 
>> data while one job is despooling to tape.
> 
> I come back on this. I've setup on director's storage Autochanger{}
> configuration:
> Maximum Concurrent Jobs = 5
> but i've set on storage configuration, in the Device{} stanza:
> Maximum Concurrent Jobs = 1
> as suggested for tapes; clearly i've only one device/tape. I've defined two
> jobs, but the first run, the second:
> is waiting on Storage "BPBKPLOMAutochanger"
> And don't start to spool data, wait there indefinetively.

Sorry, i really don't understand and i need feedback...

I've read many time that tapes are handled better as they are, sequential
media; so they need on storage:

Maximum Concurrent Jobs = 1

but in this way, if i need spooling (and *I* need spooling for tapes!) i can
run on tape jobs only sequentially: eg:
  - spooling job1 -> despooling job1 (repeated many times)
  - spooling job2 -> despooling job2 (repeated many times)
  - ...

A bright suggestion is to define different jobs and so 'interleave' that,
so when job1 is despooling, job2 can spool data.

But if set on storage 'Maximum Concurrent Jobs = 1', the storage do exactly
one job at a time. job2 wait the end of job1. Period.


I can set 'Maximum Concurrent Jobs > 1'? What i can expect from the SD? Will
despool job1 and then despool job2, or i can expect to have also the
despooling of job1 and job2 'interleaved', that i suppose is a bad thing?


Sorry, thanks.

-- 




___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Again LTO9 and performances...

2024-06-11 Thread Gary R. Schmidt

On 11/06/2024 18:56, Stefan G. Weichinger wrote:

Am 06.06.24 um 15:57 schrieb Marco Gaiarin:

Mandi! Josh Fisher via Bacula-users
   In chel di` si favelave...


Not for a single job. When the storage daemon is writing a job's spooled
data to tape, the client must wait. However, if multiple jobs are
running in parallel, then the other jobs will continue to spool their
data while one job is despooling to tape.


I come back on this. I've setup on director's storage Autochanger{}
configuration:

Maximum Concurrent Jobs = 5

but i've set on storage configuration, in the Device{} stanza:

Maximum Concurrent Jobs = 1

as suggested for tapes; clearly i've only one device/tape. I've 
defined two

jobs, but the first run, the second:

is waiting on Storage "BPBKPLOMAutochanger"

And don't start to spool data, wait there indefinetively.


What i'm missing?! Thanks.


interested as well, I need to speedup my weekly/monthly FULL runs (with 
LTO6, though: way slower anyway).


Shouldn't the file daemon do multiple jobs in parallel?

To tape you can only write ONE stream of data.

To the spooling disk there could be more than one stream.


Yes, that seems wrong:
$ grep Concurrent *.conf
bacula-dir.conf:  Maximum Concurrent Jobs = 50
bacula-dir.conf:  Maximum Concurrent Jobs = 50
bacula-fd.conf:  Maximum Concurrent Jobs = 50
bacula-sd.conf:  Maximum Concurrent Jobs = 50

Cheers,
GaryB-)


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Again LTO9 and performances...

2024-06-11 Thread Stefan G. Weichinger

Am 06.06.24 um 15:57 schrieb Marco Gaiarin:

Mandi! Josh Fisher via Bacula-users
   In chel di` si favelave...


Not for a single job. When the storage daemon is writing a job's spooled
data to tape, the client must wait. However, if multiple jobs are
running in parallel, then the other jobs will continue to spool their
data while one job is despooling to tape.


I come back on this. I've setup on director's storage Autochanger{}
configuration:

Maximum Concurrent Jobs = 5

but i've set on storage configuration, in the Device{} stanza:

Maximum Concurrent Jobs = 1

as suggested for tapes; clearly i've only one device/tape. I've defined two
jobs, but the first run, the second:

is waiting on Storage "BPBKPLOMAutochanger"

And don't start to spool data, wait there indefinetively.


What i'm missing?! Thanks.


interested as well, I need to speedup my weekly/monthly FULL runs (with 
LTO6, though: way slower anyway).


Shouldn't the file daemon do multiple jobs in parallel?

To tape you can only write ONE stream of data.

To the spooling disk there could be more than one stream.





___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users