Mike2700

When I selectively sync a folder what is the behaviour I should expect. When I add files to that folder should they be synced other devices When I remove files from that folder should that deletion be synced to other devices?

Any info on this? Also what happens when I add files in a directory that I have chosen to selectively sync. Do those files get synced?

Hi. Here are a bunch of questions and observations about selective sync. I am planning a company wide adoption of BTSync pro subscription in the next week so it would be good to see if any of our issues are on a roadmap to be improved. I have a 350Gb share with approx 1M files in approx 10 main sub directories. I've set this up as a selective sync so I can chose to sync only the subdirectories I need. How can i see which sub directories are currently syncing and which are not? I just see green ticks on all my files regardless of whether their directory is syncing or not. If I sync a directory, then stop syncing it for a period, how can I tell if it is being synced or not? Do you have any way of easily telling what is getting synced planned for the GUI or explorer integration? Also, I notice that in my peer list window when viewing the Device List list of files that are being synced I see many files that are from directories that are not included in my selective sync. I think this maybe a bug, but its not a big issue. More serious is when we setup the sync on each client a lot of the data is already distributed around our clients after using previous BTSync clients to sharing individual subdirectories. The initial indexing phase renders the clients GUIs unresponsive for up to 5 days. Can this be fixed? Memory usage is also a bit high - I have about 1.5Gbs in use for BTSync with approx 700Gbs shared. Some colleagues report up to 3Gbs of memory use which is a little high. Any plans to bring this down? Finally, the original share is a 1.4 share because the 2.0 client is not available for our server. All the clients are 2.0, would this cause problems with selective sync.

Its a big problem for our company in completing any upgrade. We're very interested in using sync commerically but our master server would have to be our win2003 server. If we go to a subscription, how will this affect our request to support 2003? I've read that subscription support requests will be treated as a priority.

When restarting the GUI can we remember the sort order of the shares? Att present it returns to default ordering each time you open the GUI.

Hi I get a not a valid win32 executable error on windows server 2003 trying to install 2.0.0.82. 1.4.0.x worked on server 2003 with the hack to use a different browser. Is there any plan to have an executable that installs on server 2003 so we can upgrade all our installs? Thanks

I just upgraded from 1.4.110 to 2.0.82 on Windows 7 x64. I have about 300Gb of data shared. I think the 2.0 version is correct but i can't check because of the GUI problems below - its the one released today. After the upgrade the UI for 2.0 is unresponsive and even reports Not Responding on occasion. Somthing it happening in the GUI thread that need to happen in the background. I guess an upgrade is going on, hopefully this will end shortly. The GUI is not usable at this point.

+1

Update: We've enabled debug logging so if the issue occurs again we will be able to report with logs from all machines.

Hi Myself and three others are using BTSync to collaborate whilst working on a very large set of files (60Gb+ each in more than 5+ shares). Our setup is external USB drives connected to laptops with folders which are being synced with BTSync. Our problem is that periodically one of the machines (not always the same one) seems to detect that all the files have been deleted (when they have not intentionally been deleted). They then get synced into the .SyncArchive of the other machines. A very short space of time later the deleting machine realises that the files are still there (or they have come back) and starts syncing them out to all the other machines. We can tell which machine did this because it doesn't have the files in its .SyncArchive - sometimes we can see in the history too. Is this a known issue, or is there anything we should be doing to avoid this behaviour. Our practice when moving our machines is to hibernate the machine with BTSync still running and the drive attached. Then unhibernate usually without the drive attached and re-attach the drive. Usually this seems fine. We are not sure that moving the machines is what is cuasing the issue yet. We have started to try to shut down BTSync before we hibernate, but this is sometimes hard to remember to do. All the laptops are windows 7 x64 with an always on windows server 2003 also syncing the same folders. Any ideas? Let me know if I can provide any information that would help figure this out. Thanks