Oh wow, it took me a few days after upgrading two systems from Debian 11 to Debian 12 to realize #borgmatic now ships a service unit and a timer unit (while I've been using good old crontab entries until now).
Anyone here using #Borgmatic? Are you happy with it?
If you're using another #BorgBackup wrapper and think it's better than Borgmatic, feel free to suggest it (and tell me why it's better.)
Plain Borg simply doesn't quite cut it for me, I'd like to have some kind of declarative configuration that I can share between machines and yet still have minor differences between them. I was about to write my own wrapper, but Borgmatic looks like it could be everything I need.
As anticipated a while ago, not amused by #borgmatic's breaking changes, like forcing --create --check to be written `create check' (despite the doc's still mentioning the old syntax).
Changing the repository syntax could be considered even nastier, as the old syntax is still supported (resulting in backups getting created) with a return code that's non-zero…
🚀 BorgWarehouse v2.0 is released and ready for Docker !🚀
✨ Launch your BorgWarehouse container to instantly have a BorgBackup server with the best webUI management interface ! Use the setup wizard to set up your BorgBackup clients in just a few clicks (#Vorta, #Borgmatic...)
📖 It's all easy, with up-to-date documentation to help users and administrators !
@borgmatic Hi, I've recently started using #borgmatic. It is an excellent tool.
Looking for some help, pls.
I've included a call to healthcheck.io, which is working well.
I see a message though saying my yaml uses a string value, which is due to be deprecated so should be replaced by a mapping.
So I've changed it to a constant, declared at the top of the yaml. That works ok, but I still see the warning about the string value & to use a mapping.
Is a mapping different from a constant?
borgmatic 1.8.3 has been released with more sensible logging logic, Grafana Loki monitoring support, recommended installs using pipx instead of pip, and more.
@borgmatic using #borgmatic (v1.7.7 on #debian 12) commands in a #systemd service of my own -- and have duplicated output in #journalctl from them: every line that #borgmatic outputs is also duplicated with an extra word "ANSWER" in it... how do I inhibit the dupes?
@borgmatic thank you so much -- reading that post now (had a hard time finding it). And many thanks for this tool, #borgmatic and #borg of course, is just awesome!