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 = ""
> }
>
>
This example implies that a separate database named "verify" should be used
as well as a user and password to connect to such a database. However, when
I looked at (I'm using PostgreSQL 8.1.9) the scripts for making / creating /
deleting, etc. (such as create_postgresql_database, make_catalog_backup,
etc.) there are no scripts specific for managing a verify-specific database.
Rather than requiring a separate Verify database, is it possible for the
"main" Catalog Resource used by the Director to be shared for Verify Jobs?
Thank you,
-H
-------------------------------------------------------------------------
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
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
