Search the Community

Showing results for tags 'version'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Resilio Sync
    • Sync General Discussion
    • Sync Troubleshooting
    • Sync for NAS (Network Attached Storage)
    • Sync Stories
    • Developers
    • Feature Requests

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 11 results

  1. Hello, Current situation: If you have an encrypted folder with RO access on PC [A], and encryped folder without R/RO access on server . And you delete or modify a file on [A], on the file goes to .sync/Archive, but it cannot be restored or shared with other nodes. I would like to be able to select on a random node , for example [A], to restore files from the archive on an other (encrypted) node, for example .
  2. Goodday, I have a need for selective versioning, at least per share. The case in point is that I have a directory for work ducments and another for VM instances I want to sync between two computers, my desktop ( a fast computer) and my laptop (not as fast, but needed when out in the field , coupled with a backup central NAS server. The image size of the VMs directory totals only 5G (Linux instances but as they run, I have a 6x multiplication in less that 24hours, synching to the central NAS/backup server. Okay, on the NAS (Linux server) I could start a separate btsync instance, but I don't have that facility on the MacOSX machines where I run the VMs on (though only one at a time using the VMs, still both the Desktop and Laptop is on for various other reasons), and to do the sync_trash_ttl globally, I loose my work document history/versioning ;( As such I want a way to specify for a share/directory how much (and or how often) I need to version it instead of for the whole instance. Extending the patch and version size settings to be per directory/share would also be handy in this regard. Come to think about it, it would be nice to also have a way to say that it should only keep a single version per day, instead of for every sync. Would be great if that is extended to a version every hour for the first day etc. but that starts to become a backup policy...
  3. hi Could you tell me if current ARM version for RPI 3 (running OSMC) still usages lots of CPU. I'm currently running some unsupported / wildcat version of Sync and I would like to upgrade to latest / supported version, but not if CPU usage still really high as I don't have cycles to spare on my little media centre. The version I'm currently using is 2.0.93 and I got it from http://debian.yeasoft.net/btsync . Cheers, Geoff.
  4. Hello everyone. I am trying to sync my Lightroom content from my desktop to my laptop for when I'm on the go. The first time, I told the Lightroom catalogue to just stay in it's normal place and I synced it normally. It saves in the user\Pictures folder on Windows. After a few days of working in LR, I saw my server space went from 600gb free to 50gb free. Every change I made in LR, it synced and created a new archive to my server. And since the server saves all changes for 45 days, I'd have hundreds upon hundreds of versions of the LR catalogue. I searched a bit and found this link https://help.getsync.com/hc/en-us/articles/204754239-Does-Sync-support-versioning- And it says: I'm not sure if this setting I found above would limit the number of total file size changes? For example, if I set it to 2000, that would give me roughly 2gb of file versions. But what happens after that? If I set it to 5000, and it keeps roughly 5gb of changes, does it begin to delete the OLDEST ones first? Normally I don't mind about the number of file versions, because most images or documents are, at most, 40mb. But my LR catalogue is 900mb, and every time I make 1 stroke or change 1 tiny thing, the whole catalogue gets backed up (which I want), but the number of versions gets out of hand. Are there any solutions anyone could think of? Thank you very much.
  5. I am brand new to BitTorrent Sync and this forum. I have a question about how to handle something I am trying to use this product for. Essentially I am using this to sync up several workstations with one another having a central server containing all data. Each work station will have selected folders based on its specific needs. The issue I have is version control. My understanding is that whoever saves the files last will be the one who retains the file changes and the person who saves first will loose their changes. Another fear I have is if somebody accidentally deletes files or a directory in their environment and the deletion spreads to all environments causing data loss. I thought about using some kind of file indexing or version control system in parallel with BTSync such as git. The issue is that I have millions of files and roughly 500Gb in data total. Git cannot handle that amount of data well and most other centralized version control systems won't really do what Im looking for. One other thing to point out is that the data being stored is all different types of files from office documents, Adobe creative files, source code, compiled files, archived files, sound, video, etc. Does anybody have any ideas on what I can do to solve this problem?
  6. hi, where can i lookup the Version of the running BTsync (Windows)? I know that it must be 1.4.103.
  7. I DO try to stay with the latest release and it is not always clear just what that is. If the MD5 hash of the latest release were included on the download page, it would make determination much easier and insure a good download.
  8. I read this on the FAQs for BitTorrent Sync: Yes, versioning is available in BitTorrent Sync. It creates and stores all the old copies of edited files for the period of 30 days (this default period can be changed in General advanced preferences - sync_trash_ttl). The versions are stored in the hidden .SyncArchive directory within your sync folder that you can open by right click on the sync folder and choosing 'Open SyncArchive'. Old versions of a file are marked by adding numbers to its name, where the file with the highest number is the latest. However, I am testing this out, and I only ever see one file in the .SyncArchive folder when the file is resaved with changes - there are no numbers appended or anything. Do I need to turn something on in the preferences/settings somewhere? Any help would be appreciated.
  9. hidden_premise

    Disable versioning

    Can I disable the new versioning feature all-together? If so, can it be done on a folder by folder basis?
  10. Hi Guys, Is anything known on 1.1.82 ? Release notes ?
  11. I noticed that versioned files only appear on the other hosts when something is changed locally. Why is that the case? Why aren't versioned and deleted files stored locally as well as remotely in the .SyncArchive folder? It would be nice to have a full 30 day history on all hosts. Is there any way to achieve that with the software as-is?