AcostaJA Posted August 2, 2014 Report Share Posted August 2, 2014 (edited) I d' Like BtSync to provide: Keep older Versions of Modified/Deleted Files, instead to fisically delete a file, Hide and Rename it as FileName.Old.X where X is the number of ancestor of the file. Keep Such Older Versions of the Sync'ed file across the Peers until some Quota or Age its reached, then fisically delete the File. To Identify Who and When a New Version of a File was created and Why (such as could be the case of an Integrity rebuild of some file) While File systems as ZFS/Btrfs provide this also at file block level, it requires a lot of CPU utlization, since requires file block level deduplication, which its cpu/memory intensive. A Way to provide this feature on an uncooperative client (those OS with deficient file sistem monitorig), could be to write block all synced files, and when an user request to edit/modify/delete a file, just copy the requested file to the saved versions repository, and then unlock the file, once the file operation its done, lock it again. these lock/unlock operations will be done at BtSync console. My 2 cts. Edited August 10, 2014 by AcostaJA Quote Link to comment Share on other sites More sharing options...
ChrisH Posted August 4, 2014 Report Share Posted August 4, 2014 BTSync already does that. Look into .SyncArchive. Quote Link to comment Share on other sites More sharing options...
AcostaJA Posted August 4, 2014 Author Report Share Posted August 4, 2014 BTSync already does that. Look into .SyncArchive.Not exactly the same way I suggest. Quote Link to comment Share on other sites More sharing options...
ChrisH Posted August 4, 2014 Report Share Posted August 4, 2014 Huh? It moves modified and deleted files at all peers (apart from the originating one) to a separate folder instead of "physically" deleting them and versions them with a number. If a configured age is reached, they are deleted. What's missing?I have to say I did not understand your last paragraph about uncooperative clients. Quote Link to comment Share on other sites More sharing options...
AcostaJA Posted August 4, 2014 Author Report Share Posted August 4, 2014 I have to say I did not understand your last paragraph about uncooperative clients.Some OS(or installs) just don't provide a system even triggered when some file system object it's modified, those are what I name uncooperative clients. I'll review on detail the feature, from as long I've read it's limited to something like a trash can function. Quote Link to comment Share on other sites More sharing options...
ChrisH Posted August 5, 2014 Report Share Posted August 5, 2014 Are we talking about remote changes that are synced via BTSync, or local changes? Because the former is already implemented and the latter IMHO is something for the OS or the filesystem. Quote Link to comment Share on other sites More sharing options...
AcostaJA Posted August 10, 2014 Author Report Share Posted August 10, 2014 *Updated the first post to expand further details on the request, which provides a sor of CVS on team enviroments. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.