Search the Community

Hello, I'm having some problem syncing folders. I set up two devices to sync via the internet over a cable connection with decent up/down speeds. One machine is running Windows 7 the other is Windows 8. Both are running the latest build of BTSync 2.2. Originally I was running 1.4 but it was recommended to me that we upgrade to the latest to take care of some peer connecting problems. That issue seems to be fixed. I was able to consistently connect the peers and sync the two folders (although it took over 24 hours to sync 7 gigs of data at an average of ~60kbps... frustrating!) Now that the original sync is done, subsequent updates to one folder do not sync with the other folder. So for example a file copied from my local sync folder does not show up on the remote drive folder - ever. I know this is the case because I can log into that remote drive and watch what is happening with it real time. I think I've done all the easy stuff, like pausing and resuming the sync on the local drive several times. The local BTSync client still sees the peer and it has read/write priveledges to that folder. I have also tried manually uploading a file to that remote drive to see if it comes back to the local drive, but that direction doesn't work either. Periodically the folder status on the local machine will change to "indexing," but no data gets transferred. Most of the time the Status field is just blank. What's weird is that the history shows the folder "finished sync with [remote peer name]" but no data was transferred around that time. I even rebooted the software and rebooted the Windows 7 PC (which is the one local to me). Nothing. I'm stumped. It looks like BTSync did an OK job of getting the files to another drive once, but incremental changes... not so much. I'm losing the love with this idea of synchronization

I'm a new user of Sync so please bear with me. We're synching two drives on two different LANs via the Internet. The sync happens beautifully, when it gets around to it. It seems to take a long time for the Bittorrent client to actually start synching once a drive gets updated. One would think that the sync would be fairly instantaneous from the point when a drive changes, but it's not. The client can sit there for many minutes before it decides to start the sync. First it starts indexing, then it it might change to "Out of Synch" for a while - sometimes a long while. Then eventually it will start the sync. Sometimes the status changes to "peer offline" even though nothing with the peers has changed. Sometimes the sync stops and the status goes back to "Out of Sync" The computers aren't going to sleep nor are they changing IP addresses or anything. Assuming nothing bad happens like a power outage, the peer availability issue usually self resolves. So is there a way to make that sync happen more instantaneously? I just turned on debug logging so I've got no data to post there. Our setup is pretty straight forward. We're synching two 4TB drives with about 7 GB of data. The Bittorrent Sync client is running on a PC with Windows 7 in one location, and on a newer PC with Windows 8 in the other location. The drives are actually attached to routers via ethernet in each location so files can be served across internal LANs in both places. Internet connectivity is cable internet with decent up/down speeds. We're running version 1.4.111 in both locations. Both PCs are set to never sleep.

My friend is having trouble with opening the installation files on his computer. They ask for permission to open, and then nothing happens. I am not sure if he uses 32 bit or 64 bit, but we have tried both installers.

I've used Sync 1.x successfully for a simple sync task. Following the 2.0 upgrade I'm unable to perform the same task. The simple task is to sync the public pictures and documents folders on two Windows 8 laptops used interchangeably by my wife and I. We travel independently a lot. We appreciate having the latest versions of shared pictures/docs available locally on whichever laptop we're using. In layman's terms (I admit that's what I am with IT matters), with Sync 1.x the public folders on the two separate laptops were directly linked. Whatever changes were made to files in the folder of one were mirrored in the equivalent folder of the other. With Sync 2.0, the architecture seems to have changed, so that changes to files in a sync'd folder in one laptop are mirrored on the other in a new folder: Users>[userrname]>Bittorrent Sync. I'm unable to link the equivalent folders (i.e., the public pictures/documents folders) of the two laptops directly. The entire contents of the sync'd folder of the first laptop are downloaded to the new Bittorrent Sync folder on the second laptop, duplicating most of the content already in the equivalent public folder of the second laptop. So while I can access and amend the public folders of the first laptop via the second, it's through the new 'Bittorrent Sync' folder created on the second laptop, not the equivalent public folders on the second laptop. How can I manage folders in the 'old' way through Sync 2.0? (Incidentally, I've tried uninstalling 2.0 and reinstalling 1.4, but 1.4 will no longer run on either laptop, despite the fresh install.) Help and advice will be most gratefully received.

Hi, Because of the poor network equipment that is on-site, we got 11 sites that needs BTS to be running out of a schedule. Those sites needs BTS to be close during business hours. When I first set-up the schedule task, all of them were functional but after a while, some of them begin to do a strange behavior. In fact, 6 out of 11 aren't working anymore. When BTS start, triggered by the schedule task, one of the share folder is showing this error: " Error: BitTorrent Sync cannot identify the destination folder" If I start BTS manually, everything is fine. 4/6 are Windows 8 Pro 2/6 are Windows 2008 R2 BTS version 1.2.82 & 1.2.87 The folder that isn't working is a mapped network drive I've already tried running BTS out of a batch file within the schedule task and it didn't work. Same behavior, BTS start but that particular shared folder isn't working. ** Note that when I run the batch file manually it work great. I also get this error in the task scheduler: 0x80070001 I did googled it and I didn't find any solution that is working with BTS With BTS 1.2.82 I got this in the log [2014-03-03 10:14:28.491] Loading config file version 1.2.82 [2014-03-03 10:14:28.554] SyncDb: Failed to init db - 4618 [2014-03-03 10:14:28.554] Loaded folder \\?\C:\000QAM_APPS [2014-03-03 10:14:28.569] SyncDb: Failed to init db - 4618 [2014-03-03 10:14:28.569] Loaded folder \\?\T: [2014-03-03 10:14:34.132] SyncDb: failed to prepare statement to query metadata - 4618 [2014-03-03 10:14:37.007] SyncDb: failed to prepare statement to query metadata - 4618 [2014-03-03 10:14:37.038] SyncDb: failed to prepare statement to query metadata - 4618 [2014-03-03 10:14:37.132] SyncDb: failed to prepare statement to query metadata - 4618 [2014-03-03 10:14:37.148] SyncDb: failed to prepare statement to query metadata - 4618 [2014-03-03 10:14:37.179] SyncDb: failed to prepare statement to query metadata - 4618 With 1.2.87, there's nothing special in the log file even with the debug enable I've tried every possible options in the task scheduler but nothing seems to work. Any idea's would be appreciated Tx

Hi, we are using BTsync on a family PC which is shared between the family members. Every user account has a share folder that is synced to the laptop of the family member in the local lan. Usually the shared desktop PC is running most time of the day and separate users are logged in at the same time. The problem is: BTsync is only started for the first user logging in. If I switch the user, BTsync stays closed for the second user, thus only the share of the first user logged in to the machine is available on the lan for synchronization. I was not able to find a solution in the forum or faq. Does anybody have an idea how to solve this problem? The last work-around I would do is to configure all sync folders in the user profile of a "sync"-user without password and ask everybody to first log in this user and then switch to the own profile. Nevertheless, I would prefer a clean solution. Best regards, Thomas