sfmcnally

Members
  • Content Count

    36
  • Joined

  • Last visited

  • Days Won

    1

About sfmcnally

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    DC
  1. 1.4.103 seems stable to me on a variety of peers, but you may have to resync everything when you move from 1.3 to 1.4, as the upgrade process is far from smooth. That was my experience anyway.
  2. I am starting to get a picture of what 2.0 have feature wise, but I still don't fully understand which features are paid and which features are free. I guess that will come out with time.
  3. If the pro version is aimed at corporate users with hundreds of peers that is totally acceptable. If you guys are trying to suddenly start charging for a product that we were led to believe was free, I imagine many of us with switch to an open source alternative as they mature.
  4. Why am I suddenly worried that one of the "features" of Sync 2.0 will be a size limit on folders in the free version. Maybe I just have a bad taste in my mouth from the "upgrade" from 1.3 to 1.4
  5. That is hardly a workable solution going forward. Add to that the fact that on NAS packages, there is often no easy way to downgrade and you have a really nice mess on your hands. Obviously I could have stuck with 1.3 forever, but that's the same as saying "I give up on future btsync development." I didn't want to do that. On another note, I'm happy to report that after re-transmitting all my data from my RW nodes to empty folders on my encrypted RO nodes, everything seems to be humming along nicely in 1.4.103. So, it would appear that btsync is once again a working solution for distributed backup on untrusted nodes. Sadly, I don't think that data from version 1.3 is ever going to sucessfully sync with a 1.4 node, but that's just my opinion from the many trials I did to attempt to avoid resending hundreds of gigs of data. Thanks to the devs for the excellent software and please pay more attention to testing upgrades and downgrades in the future.
  6. That method is the one I've used sucessfully since 1.3. Also seems to work well on 1.4.103
  7. So, this version seems to work fine, but there is one huge caveat. I suspect strongly that you can't upgrade an encrypted node from 1.3 to 1.4. I had several and none of them would sync with any version of 1.4 until I finally just used an empty folder and that finally worked. Be aware of that when you upgrade. I suspect most if not all encrypted nodes won't work without a full resync/retransmit. Note that all my nodes are now working, but I hope that in the future, forward and backward compatibility will be a high priority.
  8. Well it synced after deleting the encrypted peer and starting over. I'm starting to suspect that many of the issues are caused by the fact that 1.3.xxx does not upgrade to 1.4.xx correctly. Will try some other nodes and see what I can see.
  9. Well that easy method certainly didn't work at all. I'm now trying to sync an encrypted node in new empty folder. I'll let you know how that goes in a few days since it has to transfer ~50 gb of data. Even if the nodes are working again after starting over, I suspect that data that was encrypted and stored on an encrypted node with 1.3.xxx is not usuable after upgrading all the machines to 1.4.xx.
  10. when you say re-add, do you mean that I need to delete the encrypted data and start over or just remove the folders, uninstall btsync with remove settings checked, reinstall and readd the folder. I did the latter, but I did not delete the actual encrypted data, because it was a very large folder. I did delete the .sync folder during the reinstall. -Sean
  11. My encrypted nodes are still not syncing. I'm running 1.4.99 on all 3 computers. All windows 7 machines. 2 64bit and 1 32 bit.
  12. I've noticed this as well, but I think that it's just noting that the file exists but doesn't need to be synced. I don't know why it happens so often. It seems like a wast of resources to monitor files that often.
  13. After several days of tinkering and hoping, I can confirm that encrypted nodes do not sync. It syncs part of a 50gb folder and never finishes. This release seems no better than the last in terms of encrypted node sync engine bugs. It still frequently says no peers when the peers column lists 2 of 2. Encrypted nodes don't sync. I will say that my one read-only (not encrypted) node does seem to work ok. It doesn't always sync, but it usually will after a few hours of being out of sync. What was introduced since 1.3.109 that made the engine so buggy? Wasn't 1.4 mostly a UI update? Still a frustrated user here.
  14. I deleted all the .sync folders and removed and readded the key to each computer with the encrypted node and now it appears that it's churning through the data again and slowly syncing. I'm trying not to have to resync the 100gb folder over the internet unless absolutely necessarry. Will update when and if the sync on the encrypted folder finishes. The read only node still appears to be in sync.
  15. I have definitely updated all nodes to 1.4.99. So far I haven't removed the folders and re-added them. That's my next step. I'll report back as to how that goes. @ICE Any advice? Should I also delete the .sync folders before I re-add the keys or just remove the folder from sync and then add it back? I've already done this process in 1.4.93, and it didn't work. Folders never synced. Does anyone know if there is there any issue syncing between 32bit and 64bit nodes?