I’ve setup Syncthing to run on my ZyXEL NSA325 NAS via a third party addon (running 0.14.8, but upgraded to 0.14.9 today). I’ve also setup Syncthing on a Rpi2 with a 2.5" disk attached. The idea is to sync several folders from NAS to Rpi2 at ‘weekly intervals’.
The Rpi2 will be placed at another geographical site and function as a ‘backup location’. I know Syncthing is probably not the ideal backup solution, but having an offsite backup of data syncing over the internet though NAT routers with little effort is better than no backup at all. To prevent all to frequent updates and sync behaviour, I’ve set the scan interval of each sync folder to 604800 seconds. This should rescan all folders about once a week. At this moment, this setup is running in my own LAN @ home te see if the concept works.
The rescan interval seems to work just fine; I can tell from the webGUI that the last scan interval on separate folders is several days ago. Syncing between NAS and Rpi2 also works as expected.
The problem is that my NAS should do a disk spindown after 70min of inactivity, to limit energy consumption. With Syncthing running, my NAS doesn’t do a spindown of disks anymore. This is however only the case, when the Rpi2 is also running in the LAN. When I shutdown the Rpi2, my NAS will do a spindown of disks after 70min of inactivity. (i.e. after the last folder scan in Syncthing has finished).
Somehow, when both devices are running, they seem to keep each other ‘busy’ even when the scan interval is set to 604800 seconds (is there a max value here anyway?). In any case, it seems te generate disk I/O on the NAS, as it doesn’t preform the spindown. I assume this has something to do with logfile updates; I can see that the file ‘lastlog’ get’s updated every 10 minutes or so. I’m fairly familiar with troubleshooting Windows and network setups; but I’m a complete Linux n00b. So troubleshooting this is quite daunting.
Does anyone have the same problem and is there a solution to this?