You're welcome. I updated the systemd files to include SuccessExitStatus for error-message-less stopping of services. New PKGBUILD I just uploaded also includes a better cleanup of the entire web GUI tree, which I audited manually to really get rid of 99% of useless files.
Currently using this at home with an LTO-5 and an LTO-6 drive. System runs quarterly fulls to LTO-6 and daily incrementals to LTO-4. Tape drives are turned on/off on demand via the USB box, ZFS snapshot create/delete before/after backup run, second run after main backup run saves database+PKGBUILD+files+configuration to tape for disaster recovery purposes. Operator command is a script which beeps to alert me, should I happen to be around, unmounts tape in Bareos and ejects the tape, because it will want another one anyway, and also sends me an e-mail.
I included a bunch more files:
1) read_attribute.pl: parses binary MAM data into human-readable output. Should probably be rewritten in C. I made it work with recent Perl versions from older versions found on the web.
2) tape-label: Needs configuration in the file. Argument will be tape name. Loads tape, writes EOF to start to delete any records, rewinds, labels in Bareos, ejects tape again.
3) tape-operator: Beep, unmount, eject tape when Bareos wants a new tape. Used in bareos-dir.conf Messages resource as "operatorcommand". Needs correct storage name as first argument to know what to eject and then the usual bstmp command following.
4) tape-helper: Needs in-script configuration. As such probably only useful in my system, but just to give anyone interested an idea what can be done feature-wise. Like ZFS snapshots, USB-control, send e-mail in case drive wants a cleaning tape, read MAM chip of cartridge and send to read_attribute.pl etc.
Only thing missing is now my six config files bareos-sd|dir|fd.conf bconsole.conf and the two .ini files for the web UI. No time to sanitize right now.
Pinned Comments