Closed karamanliev closed 4 months ago
My first guess would be that the user you run snapborg
with doesn't have enough permissions to read those files displayed in the error messages. Even if you can read /.snapshots
it doesn't mean you can read all the way through to every file deep down in the file system hierarchy. Maybe you have to run the command via sudo
, as a different user or give your user the relevant permissions.
Yeah, I copied the ssh keys and config from my user to the root and running snapborg with sudo
works as expected.
Is using snapborg to backup the system snapshots intended use of the tool and is it a normal behavior to have these permission issues, or I messed something while configuring snapper
, snap-pac
and etc? I guess when I enable the systemctl
timers, they are run with elevated privileges, therefor there won't be errors?
The systemd
timers/units are run with root privileges, so that would be an option. I for myself am using snapborg only on servers, also with root privileges. If you want to backup system snapshots I think you will need to opt for one of these methods. Let's see it like this: If your user doesn't have permissions to access specific files, why should your backup solution, run by the same exact user, have those permissions?
Thank you very much for your input!
I've tested the systemd
timer while following the journalctl
logs and there were no errors. After the backups were done I mounted one of them to check the permissions and everything seemed as is.
Hello, thank you for the great tool. I have setup snapper to do automated snapshots of / and I'm trying to backup them up to a remote borg server, but I'm getting this output while doing it. Am I doing something wrong or this is expected? Can I trust these backups if something happend and I need to restore from them?
I did this, according to the arch wiki, here's the otuput for the rights of the
/.snapshots
dir:Here's also output of my
/etc/fstab
: