Ryan Novosielski schrieb:
> It's not really a huge limitation, as far as Bacula is concerned. It's a
> limitation for the USER, as you can't really look at the table and know
> what is going to happen right before the next backup. However, I
> understand why it might have been done this way, bec
It's not really a huge limitation, as far as Bacula is concerned. It's a
limitation for the USER, as you can't really look at the table and know
what is going to happen right before the next backup. However, I
understand why it might have been done this way, because the media
maniuplation reall
Martin Simmons said:
> Maybe you have something like a cron job that runs 'status dir' at 07:00.
Yep ;)
0 7 * * 5 /opt/bacula/etc/jobs.sh | mailx -s "Upcoming Bacula Jobs"
[EMAIL PROTECTED]
It's possible that I wrote and tested this script on Tuesday the week
before, thus I got the volusedurat
> On Fri, 24 Feb 2006 09:03:23 +0100 (CET), "Ralf Gross" <[EMAIL
> PROTECTED]> said:
>
> Ryan Novosielski said:
> > Do you really have NO task that kicks off at around that time that deals
> > with that pool? If so, that is rather curious.
>
> Nothing I'm aware of. This is a fragment of
Ryan Novosielski said:
> Do you really have NO task that kicks off at around that time that deals
> with that pool? If so, that is rather curious.
Nothing I'm aware of. This is a fragment of my config:
Pool {
Name = Bang
Pool Type = Backup
Recycle = yes
Recycle Oldest Volume = yes
AutoP
Do you really have NO task that kicks off at around that time that deals
with that pool? If so, that is rather curious.
_ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | | Ryan Novosielski - User Support Spec. III
|$&| |__| | | |__/ | \| _| | [EMAIL PROTECTED] - 973/972.0922 (2-0922)
\__/
Kern Sibbald said:
> On Thursday 23 February 2006 11:21, Ralf Gross wrote:
>> Volume Use Duration
>> [...]
>> The use duration is checked and the Used status is set only at the end
>> of
>> a job that writes to the particular volume, which means that even though
>> the use duration may have expired
Kern Sibbald said:
> On Thursday 23 February 2006 11:21, Ralf Gross wrote:
>> Volume Use Duration
>> [...]
>> The use duration is checked and the Used status is set only at the end
>> of
>> a job that writes to the particular volume, which means that even though
>> the use duration may have expired
On Thursday 23 February 2006 11:21, Ralf Gross wrote:
> Me said:
>
> [voluseduration ignored]
>
> I'm a bit confused about this paragraph in the documentation.
>
> http://www.bacula.org/rel-manual/Configuring_Director.html#SECTION000141000
>0
>
> Volume Use Duration
> [...]
> The use du
Me said:
[voluseduration ignored]
I'm a bit confused about this paragraph in the documentation.
http://www.bacula.org/rel-manual/Configuring_Director.html#SECTION000141
Volume Use Duration
[...]
The use duration is checked and the Used status is set only at the end of
a job that
Hi,
I created two pools with the option 'Volume Use Duration' set to 48 hours.
Volume Use Duration = 48 hours
The volume state of the tapes used for the backup 2 weeks ago, changed
their state to 'Used' on the following Tuesday. I got a appropriate
message on the console and the state was correc
11 matches
Mail list logo
