> Hi all,
>
> I'm trying to set up a Verify Job configuration and noticed in the Bacula
> User's Guide, which provides an example Catalog for running a Verify Job,
> the following:
> > Catalog {
> > Name = Bacula
> > dbname = verify; user = bacula; password = ""
> > }
> >
>
I believe this case is for a verify job for data that was never backed
up. Bacula has the ability to tell you what files have changed between
running an InitCatalog job and a Catalog job. In these jobs only the
signatures (MD5 or SHA1)  are stored or compared. I believe the
example shows you could use a separate database for this.

John

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to