The NAS is definitely slow (I previously tried running Plex on it, but it couldn’t transcode on the fly because of CPU limitations). I’m sure that’s what’s going on. I still think it would be good for Syncthing to not necessarily build the whole directory structure up front - it bottlenecks things unnecessarily. 2 days in and I’ve got 25% synced - so it’s going, just slowly. We’ll see how well it works once the first-time sync is done.
Re: CrashPlan. I appreciate the clarification! I’m still intending to use CrashPlan as my backup service, but as they now charge based on the number of machines (and I have 4; 2 laptops and an offsite desktop in addition to my main desktop) in the business plan, my thought was to use Syncthing on all but my main machine and then just pay the 10/mo for CrashPlan for this one machine. I’m already using a similar workaround to backup my NAS which isn’t supported (I got it working briefly but it wasn’t reliable). Syncthing has basic versioning, so I figured that might provide a little extra protection given the potential for slow transfers of files to the main machine.
Perhaps I’m misunderstanding the use case for Syncthing. I thought it could function similarly to the peer-to-peer “backup” (really a sync with very simple versioning) CrashPlan used to provide. I’m open to suggestions! Still working out how I want to handle the changes to CrashPlan’s service.
Thank you!