> to me it looks like InitCatalog must run twice before all changes are known
> and the regular verify behaves the way it should.
>
> (note: I have not done any changes to the system between the two jobs and
> auto update is disabled. I am not running a virus scanner or anything else
> that could t
Hello,
I see this for quite a while now and it does not seem to disappear with
2.0.1... maybe someone has the same problem?
yesterday I was upgrading my system and ran a "InitCatalog" manually
thereafter. This morning my regular verify job failed with reporting that
some hundred files have cha
Hi Kern,
I'm using Bacula whith Debian Testing.
After migrating to Bacula 1.38.3 (Dec. 22 2005) I started the Verify Job manualy.
After 10 houers I gout these Error MSG:
__
26-Dec 22:01 nas01-sd: Got EOF at file 2 on device "HP-SSL1016" (/dev/nst
Hi Kern,
the Bacula runs on Debian Testing.
Mayby I should try the 1.38.3 Version.
Am Montag, den 26.12.2005, 15:00 +0100 schrieb Kern Sibbald:
Kern Sibbald <[EMAIL PROTECTED]>
Mit freundlichen Grüßen,
Viktor Dihor
Fernwärme Ulm GmbH
Tel. +49-731-3992-267
Fax. +49-731-3992-5-267 E-
On second though after looking more closely at your output, I see you are
using FreeBSD (most likely), and FreeBSD has a problem that the SCSI guy is
working on, which prevents Bacula from opening the drive if there is no tape
in the drive. As a consequence, if you load something into the dri
Please try the beta version of 1.38.3 (22 December 2005).
On Monday 26 December 2005 12:17, Dihor, Viktor wrote:
> Hi Bacula Friends,
>
> I'm using the verify Job since Bacula 1.34.
>
> After upgrading to 1.38.2 these job still fails.
>
> Here the Config Part of the Dir config:
>
>
> Job {
> Na
Hi Bacula Friends,
I'm using the verify Job since Bacula 1.34.
After upgrading to 1.38.2 these job still fails.
Here the Config Part of the Dir config:
Job {
Name = "NAS-Woche-Verify-Volume2Catalog"
Type = Verify
Level = VolumeToCatalog # default level
Verify Job = "NAS-Weekly"
