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 time
These backups are disk-based, so this is not a timing issue with a tape
library.
From the documentation:
Max Wait Time = 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
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
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
Hello Brendan,
On Wed, Jul 8, 2015 at 12:27 PM, Brendan Martin bren...@physics.tamu.edu
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
Hello. I have problem with this.
Job {
Name = Flows
Client = prodisz-fd
JobDefs = FlowsJob
Max Wait Time = 3h
}
It's should cause canceling job if job flows stuck for more than 3h (for eg. if
no volume).
But... backup id canceled if previous backup is running for long time and flows
Hello bacula list,
I'm trying to setup a small backup concept with bacula 5.0.3
Unfortunately I ran into the same problem about one year ago with 5.0.1
I'm using file based SD.
I had one job running, accessing SD1 running, so the next scheduled job
had to wait. But it didn't wait Max Wait Time of
Op 14/06/2011 9:52, Harald Schmalzbauer schreef:
Hello bacula list,
I'm trying to setup a small backup concept with bacula 5.0.3
Unfortunately I ran into the same problem about one year ago with 5.0.1
I'm using file based SD.
I had one job running, accessing SD1 running, so
schrieb Jeremy Maes am 14.06.2011 10:46 (localtime):
Op 14/06/2011 9:52, Harald Schmalzbauer schreef:
Hello bacula list,
I'm trying to setup a small backup concept with bacula 5.0.3
Unfortunately I ran into the same problem about one year ago with 5.0.1
I'm using file based SD.
I had one
Op 14/06/2011 11:23, Harald Schmalzbauer schreef:
schrieb Jeremy Maes am 14.06.2011 10:46 (localtime):
Op 14/06/2011 9:52, Harald Schmalzbauer schreef:
Hello bacula list,
I'm trying to setup a small backup concept with bacula 5.0.3
Unfortunately I ran into the same problem about one year
schrieb Jeremy Maes am 14.06.2011 11:43 (localtime):
Op 14/06/2011 11:23, Harald Schmalzbauer schreef:
schrieb Jeremy Maes am 14.06.2011 10:46 (localtime):
Op 14/06/2011 9:52, Harald Schmalzbauer schreef:
Hello bacula list,
I'm trying to setup a small backup concept with bacula 5.0.3
Op 14/06/2011 11:50, Harald Schmalzbauer schreef:
Hello bacula list,
I'm trying to setup a small backup concept with bacula 5.0.3
Unfortunately I ran into the same problem about one year ago with 5.0.1
I'm using file based SD.
I had one job running, accessing SD1 running, so the next
Hello,
we are using Bacula 5.0.1 on Ubuntu 10.04 and use the Daily Tape
Rotation as described here
http://www.bacula.org/5.0.x-manuals/en/main/main/Backup_Strategies.html#SECTION00303
If the wrong tape is in the drive I´d like Bacula to cancel the job
after some time so it can
Hi,
I'm trying to use Max Wait Time to abort jobs that are stuck waiting for
an appendable volume. From reading the mailing list and the manual my
understanding is that this should work starting from version 3.
In my case though the jobs are not cancelled, but they stay in the queue
and block all
Hello.
I've always had jobs waiting for days for tapes.
Since I upgraded to 3.0, these jobs are failing with a message like the
following:
Fatal error: Max time exceeded waiting to mount Storage Device ...
I guess I need to increase or disable Max Wait time and Max Run Sched
Time, but I have
Can someone explain why the job is canceled.
I use Max Wait Time = 10 minutes
Output of the log-file:
03-Jan 23:27 itshas-sv11-dir JobId 1317: Start Backup JobId 1317,
Job=BCK-itshas-sv041.2009-01-03_23.23.09
03-Jan 23:27 itshas-sv11-dir JobId 1317: Using Device lto4drive
03-Jan 23:27
On Monday 05 January 2009 10:49:38 Carlo Maesen wrote:
Can someone explain why the job is canceled.
I use Max Wait Time = 10 minutes
Output of the log-file:
03-Jan 23:27 itshas-sv11-dir JobId 1317: Start Backup JobId 1317, Job=BCK-
itshas-sv041.2009-01-03_23.23.09
03-Jan 23:27
Hi All,
I have an issue with performing a backup with greater amount of data.
After a while after starting backup, the job is being stopped with
status A. I have seen that responsible for that is option Max wait
Time. After enlarging this option to 300s I was able to backup up to
10GB amount of
Hi All,
I have an issue with performing a backup with greater amount of data.
After a while after starting backup, the job is being stopped with
status A. I have seen that responsible for that is option Max wait
Time. After enlarging this option to 300s I was able to backup up to
10GB amount of
Hello.
First of all, I use Bacula 2.2.4 on FreeBSD-6.1.
I've configured all the jobs with Max Wait Time = 12h - the idea of this was
that if a job has been waiting for storage or smth too long, it will be
cancelled, so that jobs that may have a longer wait time, may start running.
I've now
To polish my Bacula (2.2.4 on CentOS5) conf a little bit, I tried to add max
wait time directive to job defaults.
More specifically:
Max Start Delay = 7200
Max Run Time = 7000
Max Wait Time = 900
So, my goal was that
- job won't start if it's delayed 2 hours
- no single job may run longer
Hi all,
Here's a quicky I couldn't find in the archives... I was looking at
both Max Wait Time and Incremental Max Wait Time. The idea being
that I may want to set an overall max wait and then have a shorter
wait time on my incrementals.
But this part of the manual has me confused as to
Hi to all,
Running Bacula 1.39
I have a schedule of jobs executing sequentially one after another based
on priority where
My Catalog Job has the lowest Priority and is executed last.
I have a situation where I added the Max Wait Time configuration
directive to all my jobs to
specifically get
Hello,
I'm running Bacula at the office to backup our workstations and some
local servers. Once in a while, a job will block the backup and
eventually, all queued jobs will be cancelled. So, according to
http://www.bacula.org/dev-manual/Configuring_Director.html, you can set
the Max Wait
Hello,
as sometimes my backup jobs fails with different reasons I would like Bacula
to leave it and start the next one form scheduled list, so I found this in
documentation.
Max Wait Time = time
The time specifies maximum allowed time that a job may block waiting for
a resource (such as
25 matches
Mail list logo
