Backup fails on symbolic links

Help
1

I’m running Kubuntu 26.04 with the version of plasma current for that release. I recently enabled backup, using the syncronize folders option, backing up two of my work folders to a NAS I’ve mounted into the filesystem.
The backup seems to run ok and all of my files are in the destination folder on my NAS. However, the notification says it failed with a long list of Operation not supported (95) errors on symbolic link files. The files it doesn’t like are in downloaded blender application folders that link out to system libraries.
I wouldn’t expect it to follow the link and try to backup the system file, but I would expect it to backup the link it’self. When I manually rsync the folder with the -a option, rsync does get the link files fine. So it must be some option the automatic process is using?
I’ve tested the backed up copies and the program fails. So this would not be a good backup.
It’s really just an annoyance as I can simply re-download the program if I ever need to..
However, the backup function will never show as successful and fail with errors, so it kind of defeats the purpose.

I don’t know if there’s a fix or workaround, but I figured I’d at least mention it somewhere and see if anyone else has seen this and found a fix.

Kevin

2

Please just provide the version, don’t make people not using your distro go looking for the information.

Which backup solution/program did you enable? Again, different distributions will package different options and you may have installed yet other options.

I’m guessing a little here because of the above mentioned issues, but a syncronize of files is not really a backup. Yes it can provide some redundancy if you immediately recognise you deleted a file, or modified a file but if you don’t recognise that immediately the next syncronize overwrites the file. The same thing can happen for file corruption, you may not even access the file but if it becomes corrupted and overwrites the synced copy you have no idea until you do go and access it again at a later date and have no way of knowing when it corrupted or how.

Ideally what you want is an incremental backup solution.