{"id":306,"date":"2009-04-21T23:27:09","date_gmt":"2009-04-21T23:27:09","guid":{"rendered":"http:\/\/blog.cyberwizzard.nl\/?p=306"},"modified":"2016-03-17T21:23:39","modified_gmt":"2016-03-17T20:23:39","slug":"release-of-new-utility-bacula-reports-09","status":"publish","type":"post","link":"https:\/\/blog.cyberwizzard.nl\/?p=306","title":{"rendered":"Release of new utility: Bacula Reports 0.9"},"content":{"rendered":"

I write a lot of code, most of it unsuitable for release to the public but this little gem is worth a public release.<\/p>\n

After using Bacula<\/a> to backup all my servers (both Windows and Linux) for some time, the large number of mailings you get when using it on a small server park drove me insane. Even when using filters to sort out new mail, it is hard to see if everything is going as it should be.<\/p>\n

Enter Bacula Reports: a mail aggregator for Bacula 2.x and 3.x.<\/p>\n

Bacula Reports consists of a faux mail command (which does not send out reports by mail but rather analyses and stores them) and a report generator which aggregates all the stored reports into one mailing with an overview and some HTML styling to make it more readable (if you don’t want HTML, modify the template to generate plain text).<\/p>\n

By integrating the scripts into the Bacula configuration at 2 points (a mail command used for sending out reports and a job to send out the combined report), the storm of daily mails changes into one neat report at the end of the backup cycle.<\/p>\n

Normal error messages and operator messages are unaffected and will be delivered as they used to be, only the backup reports per job are redirected to Bacula Reports.<\/p>\n

Requirements:<\/p>\n