Re: [Bacula-users] unable to run scheduled jobs

2025-03-15 Thread Radosław Korzeniewski
Hi, you should cancel zombie jobs. R. pt., 3 sty 2025 o 14:40 Adam Weremczuk napisał(a): > In bconsole -> status -> storage, under running jobs, I could see: > > Writing: Incremental Backup job skippy_backup JobId=5093 Volume="" > pool="lto_weekly_pool" device="Quantum LTO-8 HH" (/dev/nst0

Re: [Bacula-users] unable to run scheduled jobs

2025-01-03 Thread Adam Weremczuk
In bconsole -> status -> storage, under running jobs, I could see: Writing: Incremental Backup job skippy_backup JobId=5093 Volume="" pool="lto_weekly_pool" device="Quantum LTO-8 HH" (/dev/nst0) spooling=0 despooling=0 despool_wait=0 Files=0 Bytes=0 AveBytes/sec=0 LastBytes/sec=0

Re: [Bacula-users] unable to run scheduled jobs

2025-01-02 Thread Adam Weremczuk
Trying to manually run a one-off full backup for a single client also gets stuck at "job is waiting on Storage". On 02/01/2025 11:42, Adam Weremczuk wrote: Forgot to add I'm using LTO-8 tapes. On 02/01/2025 11:41, Adam Weremczuk wrote: Hi all, Bacula 9.6.7 on Debian 11. There has been some

Re: [Bacula-users] unable to run scheduled jobs

2025-01-02 Thread Adam Weremczuk
Forgot to add I'm using LTO-8 tapes. On 02/01/2025 11:41, Adam Weremczuk wrote: Hi all, Bacula 9.6.7 on Debian 11. There has been some mess up around Xmas time: 1. On 27 Dec some scheduled jobs exceeded max run time (18 hrs) and got cancelled. 2. On the same day, the tape drive was used fo