Is there a roadmap for the ability to save the file (full and incremental) in one directory structure and the image backups in a different directory structure. Reason being I have a need to put file backups on one NFS mounted share, and image backup in a different NFS mounted share. Right now, it looks like the image backups are stored in the root directory (of a given computer), which is used as a base for all the file level backups (stored in separate directories). I don’t see a technical reason (symlinks, etc) why these would have to be contained in the same directories, aside for it being coded this way.
I did something similar a while back and the remains are still there.
You can open backup_server_settings.db with e.g. SQLite Browser and add a new record to settings with key = backupfolder_uncompr value = the folder for image backups and clientid = 0. One problem is that it probably does not create the client folders in that directory automatically, so you have to manually create them for it to not fail.
Actually i had been able to apply a workaround, and use the post scripts to set compression on the created file backup folder, but it would really be nice to have it separated, as the characeristics for the things stored quite differ. It would be nice to have one on a slow storage for example…