(Created a new response to help visibility)
I ran another test with very interesting results!
I temporarily disabled the rootfs and bootfs backupdir like so:
For clarity on the client (at that moment):
Then i ran another incremental update, and now:
It explicitly says it it following the symlink.
BUT, when i check the backup via the webinterface i see this:
Again, the symlink is backed up as a symlink, not followed, however when i go on the urbackup server and browse the backupstore and go into the folder for that last backup, i DO see the a “.symlink_lv2” under that, if i go into that i see the file TESTDATA:
Maybe indeed this is a bug, possibly with my findings you will realize immediately what is going on Martin? Feels indeed the rewriting of the symlinks is still referring to a backupdir that doesnt follow symlinks and as such fails, in this last case it even refers to a backupfolder that isnt even part of the backup.