romeograham

OK, excellent. Thanks for the quick reply!

Hello, I have a 500GB SSD and a 1TB HDD setup in my workstation. There are a few folders (on the HDD) that I have syncing to a NAS for Backup. I am running out of space on my SSD, and I see that I have a sync.log file that is 244.2 GB!!. I can't find anything about this (quickly) in the forum. Can I delete this file? Does it perform the same function as the .archive folders (as a backup)? Can I move it to my HDD, where I have more room? Should I uninstall BTSync (which is installed on my SSD) and reinstall it on my HDD? Thanks for any help!

I'd really like this type of nested shares as well (Just like the picture that you guys have attached to this thread). My scenario: A "local server" needs to be backed up to a mirrored (off-site) server. The top-level, entire file structure needs to be synced and backed up. [This is the nested part]: individual directories on the "local server" need to be synced with individual computers in the office. The nested shares will be shared to different computers than the mirrored "back-up" server. Currently, this doesn't work with the way BTSync works. We'll have to find another solution for one of our two requirements. I don't think using .SyncIgnore will help with the top-level back-up, since we really do want ALL the files synced to the back-up. Looking forward to solutions.

So we need to install BTsync on the NAS, then generate the Secret from that machine somehow? I imagine that BTSync will only work on a machine that has the client installed on it, correct? I'm also wanting to use this to keep data backed up to a network location. thanks!