MegaByte

Thanks for the feedback, how much data are you syncing across your two servers? Any caveats for installation and maintenance? So pre-seeding wouldnt work, which I understand in some ways. Maybe syncing on the same lan and then moving servers remote? The other thing would be, do you recommend one sync job per server or 30 to 40 if there are 20GB's per folder? Basically one 600GB sync job or split them up (especially in case something needs rebuilt from corruption?

I am considering trading out a shody DFS-R deployment (A microsoft file replication solution baked into the server OS for many years now) to try BTSync. I have been reading and have only seen a few reports of BTSync crashing out on a server several months ago. I wanted to see if this was a good/bad solution and if anyone has any experience trying this or anything similar. Basically, looking for someone to pat me on the back or talk me out of it... There is about 650GB of data synced across 3 locations. The main location has a decent 35x5mb connection, the other two sites have 1mbx10mb. The file changes amount to a lot less than the whole dataset, probably 1gb per day currently in delta sync. Should I go full Mesh or setup a Hub/Spoke deal to the main office? Any other advice in general? Pre-Seeding, is there any documentation on how to do it, or is it even supported (I hope so). Will be running a test folder first..