Backintime can’t be set to react to udev – an issue that is apparently specific for Arch/Manjaro. The full issue at GitHub is here.
In brief: When in Manjaro Backintime (GUI) is set to backup after disk connection (via udev), it complains about nice when the settings dialog is OK’ed.
On Arch and Manjaro, /usr/sbin/ is not used and is a symlink to /usr/bin/, there should be no issue.
Tip: Don’t bother running Back In Time as root. Use Timeshift for system data backups and Back In Time for user data backups.
FYI, Back In Time is not actively developed, however it still works and I use it. However, since I bought a license for Baqpaq (by the original developer of Timeshift, I may move to that soon).
Yes, something like this is the plan. I am in the early stages of a migration from macOS together with a new backup strategy. For the time being I just wanted a full system outside the laptop, until a staggered-in-depth backup stands.
This looks very promising. Especially for the borg backend – I had borg among the top candidates, but not yet decided. I’ll look into what borg commands are supported.
Hello,
upstream maintainer here. Sorry for warming this up.
We might have a solution and I also got validation from a Suse security expert about that solution.
Anyway I am not able to reproduce/trigger the problem with latest Manjaro on a VM with latest development version of Back In Time (1.6.0-dev).
I am assuming I missed something in the steps to reproduce it. (issue comment) Can one of you confirm that the error is still there?
