As stated…1 terabyte solid state drive mounted in a Sabrent usb case. Thunar sees the drive fine, but “back in time” does not.
Thunar sees /run/media/kim/NoteBackup, but “back in time” does not. ?? Format is ext4.
My Thunar sees all the drives just fine also, as soon as they are plugged in - but I need to actually mount them to be able to use them.
Is the drive mounted?
Yes, it auto-mounts; just plugged the drive in and it appears. I am able to peruse the drive, and if I right-click it, unmount and “safely remove” appear in the list…
I can only test this on my not Manjaro (Mint) system -
all my Manjaro systems are VM’s, where I can’t easily attach an external drive.
I have not enabled automount on connect - I need to explicitly mount a drive.
… and when I do, it appears as a possible destination in backintime
so - there
That is all I can say about that … sorry.
Did you install backintime from the repos or is this a Snap/Flatpak? If the latter, those are containerized applications, and they have no access to anything other than the local filesystem.
If you are not using Flatpaks as stated by @Aragorn , try this tutorial:
But make sure gnome-disks is installed first.
From the repos…I downloaded gnome-disks, and followed DeLinuxCo’s plan. I can use the non-root backintime, but the backintime (root) is still a no-go: it still can’t see the drive.
I carefully checked that I had the path correctly named and was able to do a backup of my home folder using the non-root backintime. Perhaps expecting backintime (root) to do a complete backup from /root using backintime (root) was a misunderstanding on my part.
Did you had reboot ?
or
sudo systemctl daemon-reload ; sudo mount -av
@kww
I’m preparing some manjaro installations for some comparison and verification. I set up a new backintime(root) on a fairly plain manjaro installation. *This is a test.
I’m not using gnome-disks.
Backup target /etc /efi /root
Backup volume /media/BANBAN BTRFS-no subvolume
/etc/fstab BTRFS
LABEL=BANBAN /media/BANBAN btrfs defaults,subvol=/,noatime,compress-force=zstd:1,autodefrag,discard=async,x-gvfs-show,users,auto,nofail 0 0
The backup runs without any problems. I wonder why??
Of course.
1 Like
A post at the BIT Git site solved this issue by a new install of Manjaro: Backintime (root) doesn't launch on Manjaro · Issue #1252 · bit-team/backintime · GitHub
root and non-root ?
what purpose does the root access serve?
back-in-time is for user backup.
I think your issue is caused when the task runs as root and expects the device to mounted at another location.
If you used the mount point the system generates on the fly - that may explain your issue - I cannot know for sure but if/when you script a system backup e.g. running as root then you need to ensure the device is mounted at the path expected by the task.
One way of doing that is to use a common mount point e.g. /a/backup and create a matching set of units a-backkup.mount and a-backup.automount - the automount will activate the mount unit when anything tries to access the mount point /a/backup and if you devices is not available the task will fail and the event logged.
It allows to backup all users data from a single user (with root access) run. This is what I use it for. And of course, from a root access you can see all data saved and when necessary recover some file(s).
backintime-qt works, as far as I can tell
(there are two different packages:
one named backintime and one named backintime-qt)
It installs two binaries:
backintime-qt
and
backintime-qt_polkit
The latter asks for admin rights and should be able to access everything - the former doesn’t and probably can’t be used to back up what doesn’t belong to the user starting it.
The package named just backintime also installs two binaries:
backintime and backintime-askpass
None of which start for me in an Xfce4 VM.
1 Like