On 2025/12/09 16:10, Rob Gerber wrote:
Kevin,
Thank you for the update, and your kind words. I was thinking about you
today, hoped you were going to be able to get it figured out. Sorry, I
would have replied sooner but I have a bit of a head cold and don't have
much energy right now.
I know I have iterated through setting up bacula, not just once, but again,
and again, and again (different scenarios each time, tape, local disc
backup, cloud backup). It seems that there is always something new to
discover about bacula. I have found it to be very useful to document every
step I take to set up bacula, and when I think I have things where I want
them, I blow away my (testing) environment and follow my document to make
sure it is complete and does lead me to the result I want.
I would like to suggest the bacula front end, bacularis (developed by
Marcin, who is on this list also). Bacularis has helped me many times with
easy observation and control of Bacula's activity, and VERY helpful
highlighting of errors in the recent log events. Turning a little log icon
red and letting me jump to the red highlighted error lines has seriously
helped me immensely.
Https://bacularis.app
Bill A has a very helpful email reporting script. I've set it up with one
of my bacula installations so far, and its been quite helpful for
monitoring Bacula's status. I definitely need to deploy it at my other
bacula instances as well. Please note that AFAIK, baculabackupreport does
not support encryption. For this reason, I connected it to a postfix
install, and let postfix handle SSL.
Check out his other scripts as well. Drop in replacements for Bacula's
mtx-changer and tapealert look interesting to me.
Bill is also on this list.
https://github.com/waa/
Bill also has a set of dummy resources for bacula (not on github as far as
I can see, but you can easily make them yourself). The general idea is that
jobs sometimes require specification of resources they dont actually use.
For example the Verify-Job doesn't use a client, pool, or fileset, but a
valid client, pool and fileset resource are required by the bacula
configuration parser. For this reason, Bill has found it useful to create
empty pool, client, and fileset resources with the name "None", and an
empty schedule named "Manual". These dummy resources make it easier to
visually parse what is happening when skimming through the config file.
less /opt/bacula/log/bacula.log # very helpful indeed. If it happens in a
joblog somewhere, it is also logged to this file as well.
echo "some bconsole command" | bconsole | grep some-keyword # also quite
useful for searching bconsole output.
Example:
echo help list | bconsole | grep log
Test your bacula configuration files for validity with:
sudo bacula-dir -t -u bacula -g bacula
sudo bacula-sd -t -u bacula -g bacula
Never run bacula-dir or bacula-sd as root. It'll create PID, state, and
lock files in the bacula working directory that the usual bacula user will
be unable to modify.
Stay in touch, and let us know if you have any other questions. :)
Robert Gerber
402-237-8692
[email protected]
Once again, thanks for the depth of the latest reply: there's a
lot of stuff there that warrants an in-depth run through.
I will be trying out your suggestion, as regards your original
Point 3, vis:
Selection Type = PoolUncopiedJobs
tommorow, but unfortuately, there'll be a period of "radio silence"
from my end of things as I'll be away for a while, recuperatiing:
albeit not in the wake of my, all-too-brief, initial exposure to
Bacula!
Cheers again, and hope to talk with the list in the New Year,
Kevin Buckley
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
