Hey just wanted to double check w/ the administration manual, using any ZFS CoW features requires urbackup to be run as root correct? Would it be possible to, instead of using setuid, have the helper run with sudo from the urbackup user? That way theoretically the mount commands should work as expected? sudo could be configured to only allow the helper command and urbackup would not have to run as root.
Try to give it a try with a user named "urbackup”.
The only reason why I’m suggesting this is because when you install urbackup via docker, the process
urbackupsrv runs as the user “urbackup” by default.
That is how i have urbackup installed and i have ZFS enabled as well.
I have it installed natively not w/ docker but I’ll try it. Maybe the documentation is outdated?
Yeah I think it does still have this issue, at least on native installs. I get the error:
|Errors|06/14/25 15:26|Error creating hash folder. No such file or directory (code: 2)|
| --- | --- | --- |
|Errors|06/14/25 15:26|Cannot create directory /Antartica/urBackup/dellserver/250614-1526 for backup (server error). No such file or directory (code: 2)|
|Errors|06/14/25 15:26|Backup failed|
It seems to create and mount the datasets fine, and link them in. The issue is that they all seem to be owned by root:root even though the parent directory is owned by urbackup.
Looking at the source code the folder is supposed to get chowned but that doesn’t seem to be happening for some reason.
So it looks like this was fixed in the dev branch a year ago but the patch never made it into the 2.5.33 release. Fix chown for ZFS by einsibjarni · Pull Request #53 · uroni/urbackup_backend · GitHub
urbackup-server_2.5.33.0-1_amd64.deb (4.6 MB)
I rebuilt the Ubuntu 24.04 package with the ZFS fixes. If you feel safe trusting a random package from the internet and dont want to go through the trouble here it is. @uroni It would be awesome if these fixes could get into the server for next release. Thanks for all your work on urbackup!