Hello Chris,
Yes, Bacularis (and Baculum too) works with existing Bacula configuration. It does not initialize anything in the Bacula configuration during installation.
The one thing worth mentioning in this point is that Bacularis and Baculum save Bacula configuration in one file per Bacula component. They are: bacula-dir.conf, bacula-sd.conf, bacula-fd.conf and bconsole.conf. If you have never configured Bacula through Baculum/Bacularis and you use external Bacula configuration files included by '@', on first save configuration by Baculum/Bacularis all the external config files will be included to the main configs. I mean that if in for example bacula-dir.conf you have the following include line:
@/etc/bacula/my_jobs.conf
then on first saving config the configuration from my_jobs.conf will be added to bacula-dir.conf. It can have meaning for administrators that configure Bacula both manually by editing files and via the web interface that they will use configuration included by '@' from external files inside main component files. Also if there are '#' comments between configuration lines, they will be stripped.
Best regards,
Marcin Haba (gani)
That’s great,
That suggest the that if I spin up bacularis I don’t have to go through a complete configuration I can just point it at my existing bacula setup without risking it trying to overwrite anything. As a (very) long time user of Bacula I’m hoping to ease my team into the system and make it more accessible and easier for them to use.
Cheers,
Chris