Borg is a really great backup system with really awful tooling and every time I have to fool with it, it puts me in a bad mood.
@prettygood yeah, I made some wrapper scripts for borg years ago and it's a bad day if I ever have to do something manually
@prettygood I literally just started using it a few days ago and there's definitely a "we thought about including batteries but decided not to" vibe in the documentation.
@tehfishman yeah its part of why everyone either uses borgmatic, or has bash wrappers with exports all over the place, like I do. I just want to manually inspect a backup for a specific file without doing a whole ass restore.
@prettygood I haven't fully dug into borgmatic just yet. I looked at their docs which also have a link to a very lengthy sample systemd unit file and decided I didn't actually have time for that right now
@prettygood
*actual borgmatic documentation*
@tehfishman stunning recollection laptops exist.
@[email protected]
no idea about borg, i run a timer unit that creates new zfs snapshots and destroys old ones.
zfsnap2 does 95% of the work.
@mansalia I use borg for off-site versioned backups
@prettygood I've been pretty happy with restic for my off-site backups at least. It's not perfect, but it's good enough for my uses.

@prettygood Worst part is if you change the config if has to treat everything like it's fresh again and rescan the whole drive. Which is stupid, but it's not wasteful since it still dedupes for the actual file storage. Just means config changes lead to a really long initial backup just after it, but it goes back to proper incremental backups after that.

Just figured I should mention it since it's a pain point I sometimes deal with. Maybe I'm just using it wrong, IDK - luckily I don't have to change configs up too often, at least.

@[email protected] i killed borg in exchange for restic months back and have absolutely zero regrets. shit just works, borg is a nightmare to work with.