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 d
> 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 f
i'm using a seperate catalog for my verify-job because
i don't want the verify-job-records and data in my real catalog-backup
and i don't want to see these jobs in my self-created management web interface
between the real backups.
to create another catalog with different name, you have to change
Thomas and John,
Thank you sincerely for shedding some light on this subject. Its nice to
know that there is an option to use either the same Catalog database or a
separate one!
Best,
-H
On 10/16/07, Thomas Glatthor <[EMAIL PROTECTED]> wrote:
>
> i'm using a seperate catalog for my verify-job b
