On 6/17/24 11:38 AM, Adam Weremczuk wrote:
Hi Gary,
I know what you mean by "hijacking a thread" now.
I was reading that message when I decided to post my question from the
same window.
Today I cleared the tape drive with an official cleaning cartridge but
it made no difference to the error:
Hi Gary,
I know what you mean by "hijacking a thread" now.
I was reading that message when I decided to post my question from the
same window.
Today I cleared the tape drive with an official cleaning cartridge but
it made no difference to the error:
On 17/06/2024 17:45, Marco Gaiarin wrote:
[SNIP]
> > So, literaly, if one of the job fill the 'MaximumSpoolSize' buffer,
*ALL*
job involved (in the same pool, i think) start to write down spool to tape.
MaximumSpoolSize is the total space used in the spool area, by all jobs.
Once that is
Mandi! Bill Arlofski via Bacula-users
In chel di` si favelave...
> 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,
The trace output says:
> Please install a debugger (gdb) to receive a traceback.
so that's the first thing to try. The traceback might give more information
about where the problem is.
__Martin
> On Fri, 14 Jun 2024 13:41:18 +, Žiga Žvan said:
>
> Hi!
> I'm using bacula to backup
Hello.
At a site, I'm backing up several machines, most of which are clients
that are not powered on every day.
I've set up the following schedule and jobs:
Schedule {
Name="DailyFDI"
