On Thu, Jul 26, 2012 at 4:14 PM, John Drescher <drescherjm AT gmail DOT com> 
wrote:
> Here is the log:
>
>  Build OS:               x86_64-pc-linux-gnu gentoo
>   JobId:                  29107
>   Job:                    VerifyVolume_Gladwin-ds3-Job.2012-07-26_15.28.54_09
>   FileSet:                Gladwin-ds3-fs
>   Verify Level:           VolumeToCatalog
>   Client:                 datastore3-fd
>   Verify JobId:           29104
>   Verify Job:
>   Start time:             26-Jul-2012 15:28:56
>   End time:               26-Jul-2012 16:01:21
>   Files Expected:         46,577
>   Files Examined:         46,577
>   Non-fatal FD errors:    0
>   FD termination status:  OK
>   SD termination status:  OK
>   Termination:            Verify OK

Hmm. It looks like user error.

I do not have Verify Job set. I will try that.

Verify Job = Job-Resource-Name
    If you run a verify job without this directive, the last job run
will be compared with the catalog, which means that you must
immediately follow a backup by a verify command. If you specify a
Verify Job Bacula will find the last job with that name that ran. This
permits you to run all your backups, then run Verify jobs on those
that you wish to be verified (most often a VolumeToCatalog) so that
the tape just written is re-read.


-- 
John M. Drescher

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users