2.1.18 beta fixed the problem - thanks for the help!
-bradley
On 6/20/07, Troy Daniels <[EMAIL PROTECTED]> wrote:
> Hmmm... your right, there is no 2.0.4 on Sourceforge.
>
> Well according to the bug report at
> http://bugs.bacula.org/view.php?id=803 it's fixed in version 2.0.4.
>
> I'm running
Hmmm... your right, there is no 2.0.4 on Sourceforge.
Well according to the bug report at
http://bugs.bacula.org/view.php?id=803 it's fixed in version 2.0.4.
I'm running 2.0.2 and haven't had to to investigate updating it yet.
There is also a patch you can apply against 2.0.3 on this report.
O
Aah. So did forget to mention it. I'm running 2.0.3.
I cant seem to see 2.0.4 on sourceforge - are you referring to CVS head?
Thanks!
-Bradley
On 6/20/07, Troy Daniels <[EMAIL PROTECTED]> wrote:
> Hi,
>
> You failed to mention which version of Bacula you are running.
>
> However this is a kno
Hi,
You failed to mention which version of Bacula you are running.
However this is a known bug with some of the earlier 2.x versions of
Bacula. I believe it was fixed in either 2.0.3 or 2.0.4.
Basically, the problem is *when* the verify job chooses the last
successful backup to verify. With th
Hi,
I have a verify run after my backup run. The backup runs successfully,
as does the subsequent catalog backup, but then the verify job then
wants the next prior backup job.
For example, if I had a successful backup on Monday, to volume Monday,
and I again have a successful backup on Tuesday to
