I just started using Urbackup, the feature list sounds great but I cant make this work on the client side.
Both of my client and the server are Debian Buster. Everything seems to work, I can login to the server see the settings even an active backup/indexing. My issue is that the indexing is never finished, it has been like a day already and no end to this. My backup is like 17gb. Seeing that, I restarted the server and used the urbackupclientbackend with debug. The I started
/usr/local/bin/urbackupclientctl start -i
Waiting for server to start backup... done
Timeout while waiting for server to start backup
The client seems to be indexing files for couple mins (based on the console output) then it stops or seems to stop indexing files and start printing these or similar lines repeatedly without going back to indexing.
I am not sure, these are the last lines it printed before going into that repeated line mode
Bear in mind I am backing up /home/USER, I have no idea how it jumped to /lib/systemd
019-05-12 12:40:28: Not following symlink "/lib/systemd/system/mountnfs-bootclean.service" because symlink target at "/dev/null" is excluded
2019-05-12 12:40:28: Not following symlink "/lib/systemd/system/mountnfs.service" because symlink target at "/dev/null" is excluded
2019-05-12 12:40:28: Not following symlink "/lib/systemd/system/nfs-common.service" because symlink target at "/dev/null" is excluded
2019-05-12 12:40:28: Not following symlink "/lib/systemd/system/rc.service" because symlink target at "/dev/null" is excluded
2019-05-12 12:40:28: Not following symlink "/lib/systemd/system/rcS.service" because symlink target at "/dev/null" is excluded
2019-05-12 12:40:28: Not following symlink "/lib/systemd/system/reboot.service" because symlink target at "/dev/null" is excluded
2019-05-12 12:40:28: Not following symlink "/lib/systemd/system/rmnologin.service" because symlink target at "/dev/null" is excluded
2019-05-12 12:40:28: Not following symlink "/lib/systemd/system/saned.service" because symlink target at "/dev/null" is excluded
2019-05-12 12:40:28: Not following symlink "/lib/systemd/system/screen-cleanup.service" because symlink target at "/dev/null" is excluded
2019-05-12 12:40:28: Not following symlink "/lib/systemd/system/sendsigs.service" because symlink target at "/dev/null" is excluded
2019-05-12 12:40:28: Not following symlink "/lib/systemd/system/single.service" because symlink target at "/dev/null" is excluded
2019-05-12 12:40:28: Not following symlink "/lib/systemd/system/stop-bootlogd-single.service" because symlink target at "/dev/null" is excluded
2019-05-12 12:40:28: Not following symlink "/lib/systemd/system/stop-bootlogd.service" because symlink target at "/dev/null" is excluded
2019-05-12 12:40:28: Not following symlink "/lib/systemd/system/sudo.service" because symlink target at "/dev/null" is excluded
2019-05-12 12:40:28: Not following symlink "/lib/systemd/system/umountfs.service" because symlink target at "/dev/null" is excluded
2019-05-12 12:40:28: Not following symlink "/lib/systemd/system/umountnfs.service" because symlink target at "/dev/null" is excluded
2019-05-12 12:40:28: Not following symlink "/lib/systemd/system/umountroot.service" because symlink target at "/dev/null" is excluded
2019-05-12 12:40:28: Not following symlink "/lib/systemd/system/x11-common.service" because symlink target at "/dev/null" is excluded
2019-05-12 12:40:29: ClientService cmd: STATUS DETAIL#pw=hdQVbtR5u5RgQLGkbHfhpPxMDm7IZT
2019-05-12 12:40:29: rc=0 hasError=true state=0
2019-05-12 12:40:30: ClientService cmd: STATUS DETAIL#pw=hdQVbtR5u5RgQLGkbHfhpPxMDm7IZT
2019-05-12 12:40:30: rc=0 hasError=true state=0
2019-05-12 12:40:31: ClientService cmd: STATUS DETAIL#pw=hdQVbtR5u5RgQLGkbHfhpPxMDm7IZT
2019-05-12 12:40:31: rc=0 hasError=true state=0
Ok I removed the backup path and added a new one that does not follow symlinks. The issue is resolved, I am guessing that something funky was going on with the followed symlinks.
The backup was done quite happily. I am wondering why not disable symlinks by default? That seems to be the case for many sync and backup applications anyways.