finalbeta

My goal was to set up a folder on a second (windows) station that stayed exactly the same as the first folder. So I set up a read only sync between the hosts. As a matter of test I deleted a number of files on the read only member, expecting them to be recreated once the 600 second folder check timeout elapsed. However, the files do not get recreated. This is likely be design. Can this behavior be overwritten? Can I force the second client to recreate the files? I would like to use the second station as a backup host, no matter what, the second host should always recreate the original structure. (In my use case)

I'm currently evaluating BTSync to sync a folder/subfolder with several million files. The application crashed after X number of hours on both servers. Do I follow the normal procedure to supply information? (Will you have enough information?)

I'm currently evaluating the tool for off site backup purposes. (Windows based) To be able to use it this way it is currently "missing" some features. Some features however make it perfect. * Run as service. (I see it is on a todo list). * Daily reporting of transferred/failed items. * Use of Volume shadow copy to transfer locked/in use files. (If a sync could be scheduled, one might be able to implement this himself) * Bandwidth limitation for peak/off peak hours. (Currently bandwidth limitation is an on/off switch) I realize this might not an appropriate use of the tool. We however see great potential in the tool as an off site backup solution. (No need for a site to site tunnel, possibility to backup several devices to a central location, encrypted/secure connections, read only features)