Re: [Bacula-users] Bug Baculum? 11.0.5.4 after cancel JOB of COPY

2021-12-06 Thread Jose Alberto
Hi Marcin. In the bconsole it remains as canceled, status A (aborted by the user), but in Baculum it remains in Running. To remove it, I must restart the director when the jobs are not running. It only happens when I cancel JOB of type copy. On Mon, Dec 6, 2021 at 9:16 PM Marcin Haba wrote: >

Re: [Bacula-users] Bug Baculum? 11.0.5.4 after cancel JOB of COPY

2021-12-06 Thread Marcin Haba
Hello Jose, What is the jobstatus in the Catalog database for the cancelled job? Could you check if there is letter 'A' or still 'R'? You can use just the bconsole 'list jobs' command for that. Best regards, Marcin Haba (gani) On Mon, 6 Dec 2021 at 22:10, Jose Alberto wrote: > > Hi. > > Use Bac

[Bacula-users] Bug Baculum? 11.0.5.4 after cancel JOB of COPY

2021-12-06 Thread Jose Alberto
Hi. Use Baculum, 11.0.5.4 i have a Job Copy (pool vtl to pool tape),. Work fine. But if JOB of Copy is cancel, Baculum keep showing RUNNING- But "status dir" que JOB was removed. Bug Baculum? -- # # Sistema Operativo: Debian

Re: [Bacula-users] Low performance with file daemon version 11.0.5

2021-12-06 Thread Departamento de Informática - PMI
Hello everyone Investigating a little more about what might be happening, I compared the records (from the Bacula catalog in the database) of a file that was backed up by 9.6.7 and 11.0.5, without having changed during these two jobs . I noticed that the "lstat" field of the "filename" table i

Re: [Bacula-users] Why Baculum no show New Object (but yes on dir.conf)

2021-12-06 Thread Jose Alberto
Thanks Bill. That cumulative (32) is not released (reinitialized) by default? On Sun, Dec 5, 2021 at 3:05 PM Bill Arlofski via Bacula-users < bacula-users@lists.sourceforge.net> wrote: > On 12/5/21 10:15, Jose Alberto wrote: > > When the Job finished, the idle process was removed. Restart only t

Re: [Bacula-users] Low performance with file daemon version 11.0.5

2021-12-06 Thread Departamento de Informática - PMI
Greetings everyone The issue of disabling TLS didn't resolve the issue, but after the FULL backup ran last weekend, the Differential backup's performance returned to the time it used to take. Initially I thought that this happened because, at the time of removing the file daemon from the previ