Search the Community
Showing results for tags 'version control'.
In this rising world of ransomware, it would be really good to have the ability to turn on a version control of a synced folder. Now I have a simple way to ensure my critical files never fall victim to ransomware. Without version control of the content, If I sync my critical files to other PCs, if one of them gets hit by ransomware, those encrypted versions of the files are just going to be replicated to the other PCs, and thus I have now lost those files to all locations. With version control of content, if one of the PCs become infected by ransomware, and the files are encrypted and replicated, I am still safe. I can go to one of the PCs that is not infected with the ransomware and I can restore the files to the pre infected/encrypted state. This makes BitTorrent Sync a very powerful tool in the fight against the rising world of ransomware. It ensures my critical files are always backed up, but because the other PCs folders are under version control, it does not matter if encrypted files get propagated to them. Aside from ransomware, it is a nice tool to ensure that items are not mistakenly lost or deleted. It becomes very easy for BitTorrent Sync to do this version control. As it updates files it saves the differential so that it can efficiently store old copies. Then provide a UI that allows someone to see a timeline of changes to the folder and move back in time to get at older versions of the files. Bottom line, I have been looking for a good solution to ensure I can recover from ransomware without being held hostage to them. BitTorrent Sync would be a good solution if it had version control of folder content.
Hello. I am using Bittorrent Sync to sync my Win laptop and my Mac desktop. I use Mercurial as my versioning system (SCM). Mercurial creates in its repository several files that have "~2e" at the beginning of their filenames. These files are located inside the .hg folder used to maintain the repository. Unfortunately, Bittorrent Sync does not sync these files. Executing "hg verify" confirms that the synced repository (the one created by Bittorrent Sync) is corrupted. I made a comparison between the original repository and the synced repository (the one created by Bittorrent Sync) and the only files missing are those starting with "~2e". Manually copying them from one repository to the other fixes the problem. Files starting with "~2e" do not seem to have any permission blocked; I could copy, delete and move them without any issue. To replicate this problem just create one Mercurial repository, with at least one commit, and sync it with Bittorrent Sync. You can check the integrity of a repository by executing "hg verify". "~2e" files are inside the .hg folder. I hope you can check this issue. Thanks.