• Content Count

  • Joined

  • Last visited

About monroejoe

  • Rank
    New User
  1. I wish you could schedule upload bandwidth usage. If you've ever used uTorrent, it handles this nicely. The GUI they use for scheduling is perfect, with the colored boxes you click on. After a certain hour, say 5PM, I wish to increase upload bandwidth available to BTSync. During business hours, reduce it. A few of my clients are schools and have a paltry 128kbps upload cap (free "municipal" cable internet provided by Time Warner to schools). I would like to max that out at night or sometimes I have issues getting all their data to sync within a 24 hour period. Eventually on a day they don't create much data it catches up, but I would like to help it out where I can. I think this feature would be useful for a lot of people. My usage: I am using BTSync on a server, with ~15 clients connected. My server uses read-only keys to make a backup of my client's data. In the end it works much like carbonite. It has been stable for the last few months and works nicely. I think since I use read-only keys I have avoided the bugs people have reported where certain files were overwritten, things like that. We used to use rsync under Windows/cygwin, but it was quite clumsy and I was always running into permission issues and the rsync hung a lot. Thank you for making BTSync!
  2. I use the read-only function, and I would also expect the read-only member to receive a new copy from the 'source' host. I would expect read-only to be akin to a "one-way' sync. If I delete a file, I would want it re-created.
  3. * File versioning (I know it's planned) * an option to automatically upgrade the client
  4. Using v1.0.134, and syncing around 30 folders containing a total of 200,000 files my BT Sync has started to hang. It does it every time now. Memory usage peaks at startup (1.2GB-1.5GB) then settles down to 800-900MB. I run BT Sync on one machine using read-only keys from client machines each having a few shares. Total about 10 machines, 30 shares. Force-closing the hung app has led to some of my peers' data files being renamed to .!sync and I believe in one case it even deleted one of my Quickbooks files. I am 99% certain it was BT Sync. Some of the other QB files had the .!sync as well. I tried to do a full dump using Process Explorer, but gave up after waiting over an hour for it. I have never done a full dump before, is that fairly normal for a process using a gig of ram? Willing to test my setup in any way you want me to for bug reporting. If someone can tell me if that is normal I will try again. 10 clients, mostly Server 2008 R2 servers, some Windows 7 64-bit with ~3 shares each, 200,000 files 1 "server", Server 2008 R2, using client shares in read-only mode ~2TB of data in total