On 09/06/2020 11:24, Spadajspadaj wrote:
Hi there.
I'm wondering whether there is a reasonable way to prevent bareos from
scheduling jobs from same client in quick succession.
Here's what I mean. We have a bareos setup with a single tape drive. The
jobs are scheduled daily with Inc/Diff/Full
On 07/06/2020 14:35, Oleg Volkov wrote:
Hi, All
According to "man bareos-fd" there is "-d nn" option to set up debug level.
Do anybody know what "nn" should be ?
I usually use 150 or 100. You can check the source code for debug
messages to see their level is you know where your issues are hap
; device="AWS_S3_1-01" (AWS S3 Storage)
spooling=0 despooling=0 despool_wait=0
Files=1 Bytes=1,334 AveBytes/sec=0 LastBytes/sec=0
FDReadSeqNo=29 in_msg=20 out_msg=6 fd=367
--
Andrei
On Tuesday, 19 May 2020 10:23:11 UTC+2, Andrei Brezan wrote:
>
> Hi,
>
> Running on 1
Hi,
Running on 18.2 I have a failing backup that eventually hogs all the slots
on the SD. What I can see in the job log is:
19-May 06:47 bareos-sd JobId 3693: Releasing device "AWS_S3_1-01" (AWS S3
Storage).
19-May 06:47 bareos-dir-alxp JobId 3693: Fatal error: Director's comm line
to SD dropp
gt;
> For example: The script is located on the client and I want to execute it
> from it?
>
> sexta-feira, 6 de Março de 2020 às 16:32:46 UTC, Andrei Brezan escreveu:
>>
>> You need to put the script as the value:
>>
>> RunBeforeJob="/path/to/my/script"
You need to put the script as the value:
RunBeforeJob="/path/to/my/script"
On Friday, 6 March 2020 16:52:26 UTC+1, Goncalo Sousa wrote:
>
> So as far as I know I add the option: RunAfterJob=yes and RunBeforeJob=yes
> in bareos-dir.d/job but how do I call the script?
>
>
>
--
You received this
tions that
you have there.
--
Andrei
On Thursday, 20 February 2020 16:19:11 UTC+1, Goncalo Sousa wrote:
>
> Thanks. But in which file?
>
> quinta-feira, 20 de Fevereiro de 2020 às 14:37:41 UTC, Andrei Brezan
> escreveu:
>>
>> Hi Goncalo,
>>
>> If you u
Hi Goncalo,
If you use
https://docs.bareos.org/Configuration/Director.html#config-Dir_Job_RunAfterJob
and specify "Runs On Client = Yes" then the script needs to be present on
the client you are backing up. If "Runs On Client = No" then the script
needs to be present on the director to run.
Y
One option would be to run bareos-fd with the debug flags "-d nn -dt -f".
I've found that debug level 100-150 suffices most of the times.
--
Andrei
On Tuesday, 28 January 2020 17:03:55 UTC+1, Dan Broscoi wrote:
>
> HI,
>
> I'm starting to get used with the mysql dump plugin and I have
> succes
The percona plugin was moved to base recently
(https://github.com/bareos/bareos-contrib/commit/2405a3b399c7eea7842389a1559786ccf5fbee86)
and you can find it in
https://github.com/bareos/bareos/tree/master/core/src/plugins/filed. Most
likely the documentation was not updated.
--
Andrei
On We
Hi,
It seems I'm not able to run concurrent jobs, basically this happens when I
try to run two jobs at the same time:
Running Jobs:
Console connected at 14-Nov-19 10:27
JobId Level Name Status
==
393 F
11 matches
Mail list logo
