I mentioned rclone and its mount function as it's an alternate method of accessing Seafile's backend. So if Seafile clients and web interface are somehow inaccessible, you can use rclone mount to "reassemble" the chunked data and then recover or copy to another location as needed.

The best way I can describe the phone example is that each Seafille client is a portal to the data on the Seafile server. I have it setup like this:

• Documents - MBP (macbook pro)
• Documents - Note10Plus (my phone)
• Documents - Pop (primary desktop running Pop!_OS)

From my phone I can pull any data in any of the 3 libraries without needing to sync the entire thing to each device, which is what Syncthing wants to do by default. I understand there is an ignore function but from what I can tell you'd have to manually mark quite a few folders as such so you don't sync all data to each client.

One scenario I tested last night was using rclone mount on the server, which "un-chunks" the data back into whole, flat files and mounts it in a temporary folder. I then used rclone to copy it to a Backblaze B2 bucket. Which now has fully assembled flat files sitting as a backup in B2 storage. My thought is to script that function because damned if I can't seem to get database dumps to work properly when performing backups on pretty much any self hosted product that uses them. Still learning though.

That is probably way more info than you needed to answer your question, sorry about that.