Hello.
I noticed one thing today.. a big full backup was ran on friday, so it wasn't
completed 24 hours later, but when the next job's time arrived, it wasn't run.
I was very surprised, because I expected it to run as it has been the case
without "allow duplicate jobs = no" with Bacula 2.x. Whe
"Scott Barninger" kirjoitti viestissä
news:200905030813.37077.sc...@barninger.com...
> Bacula-3.0 RPM Release Notes
> 02 May 2009
> D. Scott Barninger
>
>
> Release 3.0.1-1
>
Seems to build nicely a binary rpm for CentOS 5.3 x86_64 / MySQL.
And so does install too, the first test backup run did
Bacula-3.0 RPM Release Notes
02 May 2009
D. Scott Barninger
Release 3.0.1-1
This release incorporates a number of significant changes since 2.0.
These release notes refer to the rpm packaging only.
Please refer to the release notes and changelog in the
tarball or on sourceforge for complete inf
On Saturday 02 May 2009 23:18:02 Silver Salonen wrote:
> It looks like the script hangs, but I can't see anything that could possibly
> hang in the script (anything besides waiting for bacula-dir's output).
I meant bconsole's output here :)
But I don't think it's the case anyway, because what h
