No matter how many times I set lan_encrypt_data to false on the 2.3.1 64-bit FreeBSD release, it reverts to true when I restart btsync. I've waited much longer than config_save_interval but the behavior remains the same.

The bottleneck for sync speed will be your internet bandwidth. Sync does not impose bandwidth limits unless you tell it to. To keep folders where you want them, you need to read and understand the help guides for setting up Sync and managing folders, and recognize that you want to start all clients in Disconnected mode (if you're using Pro). This will give you the opportunity to choose where to place each shared folder. As for reliability, there's no such thing as bug-free software, so you should continue to maintain backups of everything you consider important, and start out syncing a subset of your data to see how it goes before you go all-in.

I would say the major caveat is that a clean install may give better results than an upgrade, therefore, if you plan to use version 2 at some point, you might be better off starting with version 2 on the third machine and clean installing version 2 on the others.

This is probably the best place to start: http://help.getsync.com/customer/portal/topics/769733-troubleshooting-2-0/articles I haven't tried 2.0 yet, so this is just speculation, but my guess is that you'll have better luck completely removing Sync and all related data and doing a clean install of 2.0 on all devices. When I upgraded from 1.3 to 1.4 it was a disaster until I did that.

Version 2.0 is not a minor upgrade from prior versions. http://help.getsync.com/customer/portal/articles/1902649-sync-2-0-overview http://help.getsync.com/customer/portal/articles/1901245-what-s-new-in-sync-2-0 And you probably want to choose door #2, since it's your first Sync 2.0 device.

One of the key benefits of the identity model is to make it really easy to get any of your folders onto any of your devices. You can set devices with the same identity to not automatically sync everything, but if you want to restrict what's actually available to a device, as far as I know, a different identity is the only way.