These backups are disk-based, so this is not a timing issue with a tape
library.
From the documentation:
Max Wait Time = The time specifies the maximum allowed time
that a job may block waiting for a resource (such as waiting for a
tape to be mounted, or waiting for the storage or fil
On 09/07/15 03:06, Ana Emília M. Arruda wrote:
> Hello Brendan,
>
> If you're working with tape libraries, I would recomend you to slightly
> increase this value. There are three device directives (maximum
> open/rewind/changer wait) that defaults to 600 seconds. So maybe you're
> not giving enough
Hello Brendan,
If you're working with tape libraries, I would recomend you to slightly
increase this value. There are three device directives (maximum
open/rewind/changer wait) that defaults to 600 seconds. So maybe you're not
giving enough time for your volumes being mounted by Bacula.
About you
Here are the logs for the jobs involved.
07-Jul 22:15 backup-dir JobId 542: Fatal error: Max wait time exceeded. Job
canceled.
07-Jul 22:19 backup-dir JobId 542: Bacula backup-dir 5.2.6 (21Feb12):
Build OS: x86_64-pc-linux-gnu debian jessie/sid
JobId: 542
Job
Hello Brendan,
On Wed, Jul 8, 2015 at 12:27 PM, Brendan Martin
wrote:
> I have a Bacula Director 5.2.6 running on Debian 8.1.
>
> To avoid an excessive delay in the backup schedule in the event of
> insufficient volumes, I added a Max Wait Time value of 600 (seconds) in
> the JobDefs for a coupl
I have a Bacula Director 5.2.6 running on Debian 8.1.
To avoid an excessive delay in the backup schedule in the event of
insufficient volumes, I added a Max Wait Time value of 600 (seconds) in
the JobDefs for a couple of clients. Jobs for those clients
subsequently were cancelled immediately u
