Arch Linux User Repository

@derdeagle Unfortunately, the problem could not be recreated. On standard packages, assembly occurs without errors, perhaps non-standard packages are used in your system. Alternatively, try updating your system with pacman -Syu

@derdeagle You can try https://seitics.de/files/bareos.zip which I just updated with my latest changes. Unzip into a directory and makepkg -Ccf should build a clean, single, complete, small, package.

This build has completed a 20 LTO-6 tape spanning backup with 48 TB of data with no issues a couple weeks ago.

I have also extended functionality to use ZFS snapshot names unique per job, so while job 1 runs a full backup to a tape pool, job 2 for a different drive but for the same ZFS dataset will not interfere, because it will create/delete its own snapshot. Bareos should really only be used with a snapshotting-capable filesystem. Every else is just not elegant.

Passwords are preset randomly (using pwg helper, supplied) in configs, should of course be changed to something completely different.

I am glad you adopted this project. Unfortunately I cannot build it, below is the error message.

[ 92%] Built target test_backtrace
[ 92%] Building CXX object core/src/tests/CMakeFiles/sd_reservation.dir/sd_reservation.cc.o
/home/username/.cache/yay/bareos/src/bareos/core/src/tests/sd_reservation.cc: In function ‘void WaitThenUnreserve(std::unique_ptr<TestJob>&)’:
/home/username/.cache/yay/bareos/src/bareos/core/src/tests/sd_reservation.cc:148:21: error: ‘sleep_for’ is not a member of ‘std::this_thread’
  148 |   std::this_thread::sleep_for(std::chrono::milliseconds(10));
      |                     ^~~~~~~~~
make[2]: *** [core/src/tests/CMakeFiles/sd_reservation.dir/build.make:76: core/src/tests/CMakeFiles/sd_reservation.dir/sd_reservation.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:3380: core/src/tests/CMakeFiles/sd_reservation.dir/all] Error 2
make: *** [Makefile:146: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: bareos (bareos-common bareos-filedaemon)

I am using cmake 3.23.1-1. Could you please take a look into this and help resolve it?

Thanks @bsdice

To please the r/datahoarder crowd, I have put up ten screenshots of the web UI with a brief explainer: https://seitics.de/files/bareos/screenshots/

There's a new test version up at https://seitics.de/files/bareos/bareos.zip and I zipped up all files for easier download. Single file access is still possible at https://seitics.de/files/bareos/. I also changed the mime-type on the web server to text/plain so if you click on a file, it will show in the browser as a preview and not annoyingly download right away.

My example configs and example scripts are now part of the package, instead of being bystanders. Can be found in /etc/bareos/examples. Dito for the NGINX config, which is now a single file. I made a README also in this directory to explain more concepts of the examples. Cleaned up tape-helper, with settings now at start of the file. Bunch more PKGBUILD bugfixes.

If you populate /etc/bareos with working

bareos-dir.conf
bareos-fd.conf
bareos-sd.conf
bconsole.conf
configuration.ini
directors.ini

files things should start to work pretty fast.

Well let me know what you think and if you could get it to work.

OK I spent the evening fixing things...

Download is again available at https://seitics.de/files/bareos/

• All changes are now fully AGPL3 compatible.
• The default is now a non-debug build, resulting in a 5 MB .zst-archive for everything (neat!).
• CAP_SYS_PTRACE capability is removed for security reasons in non-debug builds.
• Explained and extended optional deps more.
• PKGBUILD will now include all AUR files in the package (/etc/bareos/pkgbuild). This may seem weird but it will allow you to copy the single directory /etc/bareos off to some other place, and you will have everything necessary to bootstrap your server back into life. This is especially helpful when you need to stay at the installed Bareos version during disaster recovery.
• I included a few nginx snippets in nginx/ to help people understand how to get the web UI going quickly.
• Also included are now sanitized configuration files which I personally use, see etc_bareos/. bareos-dir.conf contains some more lenghty explanations.

LTO is a solid and safe backup technology. I'd hope with a bit of mentoring and polishing of this package people will appreciate this too and spin up a trial in their own computer landscape.

#Arch #LTOultras ;-)

@wcasanova I know, and I am sorry. I had to take it down because after reading the AGPL3 license text I realized some patches might be in violation. Other things taking precedence I can't work on this right now. Some patches may be substitutable with deletion sequences in PKGBUILD which have no origin in the source code unlike patch files, so could possibly be distributed. But if you run this at your university or CERN or something, with others accessing it, you would again be in violation. On the other hand I really can't have my browser phone home to the Bareos guys every time I open the web UI. This being Germany which has overtaken litigious USA on the right, I need to find a precedence-proofed solution.

@bsdice, the new changes you mention are no longer available.

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.