• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by mrmachine

  1. Would you mind sharing what those other solutions are? I've recently talked with the creator of CCC and it offers some protection against bitrot on the destination volume, but still has the same problem of propagating corruption on the source to the backups.
  2. I don't use Sync as backup. I have CCC to an external bootable HDD and Arq (to the ZFS NAS) for that. But if Sync will propagate bitrot to the ZFS NAS, because ultimately all the machines I actually use daily don't have any protection against bitrot, then it's still a manual process of discovering the rot to begin with, and then searching incremental backups for the last good copy. Doesn't Sync periodically index all its shares to determine if it is missing any files from the pool and sync them? I seem to recall with BitTorrent in general, if you modified some local data the torrent app woul
  3. So there's basically nothing that can be done about it... All devices need to have protection against bit rot for the pool to be safe?
  4. Getting back to the feature request, is there any chance the BitTorrent Sync could propagate bit rot to other clients? I have a ZFS NAS where I store most things, so I feel safe that it is protected against bit rot. But I want to sync some of its files to an iMac and a MacBook, which run JHFS+ file systems, which are susceptible to bit rot. If my iMac or MacBook do suffer from bit rot, is there any way that BitTorrent Sync will detect that as a legitimate change and sync the corrupted file it back to the ZFS NAS and all other devices, thereby negating the bit rot protection provided by ZFS
  5. It would be great if BitTorrent Sync allowed earlier general patterns to be negated by later more specific patterns. This would allow users to choose between whitelist and blacklist behaviour for IgnoreList and StreamList. For example: # whitelist, only sync streams listed below # blacklist, sync all streams except any negated below*! Also, support for double asterisk glob pattern matching would be great. For example: # IgnoreList/Some/**/Path Would match both: Some/Foo/Path
  6. If I allow all streams to sync with "*", can I then subsequently negate some streams with a more specific rule? Much like Synching allows a more general match to be negated by a more specific one with a preceding "!". This would allow users to choose either whitelist or blacklist behaviour. E.g. # whitelist, only sync streams listed below # blacklist, sync all streams except any negated below*!
  7. The ".bts" links are NOT analogous to the traditional "selective sync" option that many people are asking for. It is a great feature for sure, but it is very different in behaviour.
  8. Seems that the default list of xattrs mentioned in the KB and this thread has changed. It no longer syncs FinderInfo, and a few others. The default is now only: I am only syncing between OS X Yosemite clients, and I would like to make sure that all folders sync as many xattrs as possible, excepting any that are detrimental. Specifically, I like to set alternative folder icons and I'd like these to be synced rather than having to set them again on every client. But I have about 10 folders shared,
  9. Currently, a folder is shared and will appear on my other devices (using their default sync setting) as soon as I add the folder to share or select "Share folder with BitTorrent Sync Alpha" from Finder. It will appear in the default folder (if default sync setting is "connected" or "sync") with the same name as on the system it is being shared from. It can be renamed on the other devices once it is sharing, or its destination can be chosen if the default sync setting is "available", but using the same name as the existing folder as the default can be confusing. For example, if I have sever
  10. Definitely, it would be great to have an easy to use GUI to manage SyncIgnore, rather than having people edit the file by hand. It should include a collapsible tree view of all files and directories in the share (whether or not they are synced to this device). All files should be checked by default, which means they are NOT included in the SyncIgnore file. If a file is unchecked by the user, then it is added to the SyncIgnore file. This should only affect the current device. The UI could also have a second area where users can enter glob or regexp patterns to be added to SyncIgnore.
  11. So because "Icon?" is ignored, folders named "Icons" is also silently ignored? I agree this is a problem and surprising behaviour...
  12. Thanks for the reply. So it sounds like if I am syncing a few large files, then there could still be a little duplication but not too much. But if I am syncing many small files (e.g. a folder of Photos, with each photo being under or just over 4MB) then I am very highly likely to be sending the same whole files to both H1 and H2 at the same time. This seems to be the case, as when I watch the transfers window, BTSync appears to be working it's way through the file list sequentially, and so I often see the exact same small file being transferred to both H1 and H2 at the same time. Effectively s
  13. I'm using the iOS app so I don't need to carry a USB stick anymore. I'd like to have a "Transfer" folder on my computer that syncs via LAN only, shared that to my iPhone, and also at home (also LAN only). I copied a 7GB file into "Transfer" at work, and I have the iOS app open. I have "automatic sync" enabled. I see the file shows up, and the progress bar appears, but nothing is being synced. Once every minute or two for a second or a fraction of a second only the little black bar showing up/down speed appears in the iOS app and a transfer appears on the OS X app, but then it disappears. Why i
  14. I have two machines on my home LAN (H1, H2) and one machine at work (W1) that all sync the same folder. When I add files to (W1), I am seeing that BTSync is uploading to BOTH (H1) and (H2) at the same time. My upload speed is limited (ADSL). Is this uploading the same data twice (to H1 and H2)? Or is it uploading different data (H1) and (H2), which then sync with each other over the home LAN? I can see the same file being transferred to both machines, and the file is under 4MB, so I assume it is uploading the same data twice? I saw in the FAQ that I can limit a folder to sync only via LAN by d