efficacy

And another data point. Windows decided that the XP box needed an update, so I did that and rebooted. When the system came up it automatically restarted btsync, which quickly completed the problematic SANY0077.MP4 file and is now (fingers-crossed) chugging away at 1.5-2MB/s transfer. I'll see how far it gets this time.

Hmm. Thanks for that suggestion. I hadn't thought about RAM. It looks like btsync is using over half the RAM, but it's hard to tell if that is causing problems. "top" says: Mem: 123428K used, 2104K free, 0K shrd, 23752K buff, 69312K cached CPU: 1% usr 0% sys 0% nice 98% idle 0% io 0% irq 0% softirq Load average: 0.33 0.14 0.09 PID PPID USER STAT VSZ %MEM %CPU COMMAND 11880 1 root S 73376 58% 1% ./btsync 1747 1746 root S 13136 10% 0% /usr/bin/php-cgi 1525 1 root S 12288 10% 0% mt-daapd 1371 1 root S 11112 9% 0% mail_daemon 1545 1 root S 10112 8% 0% inotify_upnp 9962 1597 root S 7816 6% 0% smbd -D 1597 1 root S 7092 6% 0% smbd -D 1603 1597 root S 7092 6% 0% smbd -D 1630 1 root S 5896 5% 0% /usr/bin/afpd 1550 1 root S 5160 4% 0% /usr/sbin/upnp 0 D-Link Corporation http://www.dlink.com/ D-Link 11968 4052 root S 5108 4% 0% sshd: root@pts/1 11970 4052 root S 5088 4% 0% sshd: root@notty ... I have also now also sent an email to sync@bittorrent.com with attached logs as suggested above. Looking at the log on the NAS it does seem to be in some sort of error loop: [20130611 09:39:11.316] Found peer for folder /mnt/HD/HD_a2/backups/pictures 009297CAB5F628B100C692DD0BDB40DD6ADE5CA4 192.168.0.3:19272 direct:1 [20130611 09:39:12.321] Torrent SANY0077.MP4 status: 137 error: <NULL> meta: 1 [20130611 09:39:12.322] Sending broadcast ping for share 05C21D03FF23319147324CE635A2B248BA66BE88 [20130611 09:39:12.322] Got ping (broadcast: 1) from peer 192.168.0.3:19272 (009297CAB5F628B100C692DD0BDB40DD6ADE5CA4) for share 05C21D03FF23319147324CE635A2B248BA66BE88 [20130611 09:39:12.322] Found peer for folder /mnt/HD/HD_a2/backups/pictures 009297CAB5F628B100C692DD0BDB40DD6ADE5CA4 192.168.0.3:19272 direct:1 [20130611 09:39:13.328] Torrent SANY0077.MP4 status: 137 error: <NULL> meta: 1 [20130611 09:39:13.328] Sending broadcast ping for share 05C21D03FF23319147324CE635A2B248BA66BE88 [20130611 09:39:13.329] Got ping (broadcast: 1) from peer 192.168.0.3:19272 (009297CAB5F628B100C692DD0BDB40DD6ADE5CA4) for share 05C21D03FF23319147324CE635A2B248BA66BE88 [20130611 09:39:13.329] Found peer for folder /mnt/HD/HD_a2/backups/pictures 009297CAB5F628B100C692DD0BDB40DD6ADE5CA4 192.168.0.3:19272 direct:1 The <NULL> does not look like it should be there! Thanks, Frank.

Just adding my own experiences with this. I set it up to back up ~46GB of photos and videos from my Windows XP PC to a D-Link DNS-320 NAS box on my local network. At first everything was great - good transfer speeds and clear indication of what was going on. After about 6GB though, btsync just seemed to get bored with the whole business and just stopped transferring. I have found that killing and restarting the btsync process on the NAS wakes things up for another few minutes, but it inevitably seems to stop again soon. I hope this can be fixed soon. At the moment, with all this manual intervention, I don't feel that I can trust btsync as a backup solution