On Monday, 29 May 2017 13:00:45 UTC-6, Stan Cruise wrote: > On Monday, 29 May 2017 12:49:16 UTC-6, Dakota Pilot wrote: > > On Monday, May 29, 2017 at 2:26:55 PM UTC-4, Stan Cruise wrote: > > > On Monday, 29 May 2017 01:02:17 UTC-6, Joe Nash wrote: > > > > Somewhere in the documentation it says the scripts will use the > > > > environmental variable "db_name" if it exists. If it does not exist, > > > > then scripts will fall back to the default. Search the documentation > > > > for db_name. It's in there somewhere. > > > > Under /etc/bareos-dir.d/catalog is a file called MyCatalog.conf which > > contains the information for the default MyCatalog. You can create your > > own MyDatabase.conf (or whatever) file for your database.Then in the jobs > > resource you can specify Catalog = MyDatabase and Bareos will use your > > database. I haven't tried it but the docs indicate that is what should > > happen. > > Yes I did define a new Catalog, and I referred to it in the Client .conf > file. In the docs for the Job resource (9.2), the Catalog directive indicates > : "This specifies the name of the Catalog resource to be used for this Job. > When a Catalog is defined in a Job it will override the definition in the > Client." I did not specify it in the Job, expecting the Client to take effect. > I can try this in the Job to see if it works.
Just to be clear, once the db is created, the Catalog definition in the Client works fine. It even works in webui (after adjusting Directors.ini). My discussion is creating the db in the first place using the scripts. -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
