-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Versioning / Conflict resolution #670
Comments
Some backends support this transparently. See versioning in S3. I think google cloud supports similar. |
I'm interested in it for ACD personally, as it will let me store 6TB of photos for free with my prime subscription Peter Dolkens
|
Is this a dupe of #18? |
@leocrawford - Reading through that whole thread, I think #18 would address my needs. Slightly different implementation, but seems fine to me. Interestingly, for ACD at least, there are slight improvements that could be made to #18 as ACD lets you reference the same file in multiple "directories" - so you could actually have a complete filesystem in each "revision" My only question is how well the proposed solution will work for multiple changes in any given timeperiod. Are versions created when rsync is run, or only on-demand, etc. |
Does it? That is very neat, so you can do a proper rdiff-backup (http://www.nongnu.org/rdiff-backup/) type of operation, without symlinks. Nice! I'd suspect that it would be snapshot based |
My plan for this is to implement #98 then implement a seperate higher level Each time you ran the I will spec it out a bit later |
@ncw : can you make the rclone backup command not dependent from the underlay technology ? ( We can read S3 previous Version above), but using this is going to make more complex the management and would be based on what is under the hood. |
rclone now supports --backup-dir which with a tiny amount of scripting gives all the tools necessary for incremental backups. I do intend to wrap it in a easy to use command at some point. |
Can we please get a way to automatically archive old versions of a file, as new versions are uploaded?
At the moment, I'm using a bespoke C# app I wrote which has the following workflow:
This provides simple version history for the remote files.
The text was updated successfully, but these errors were encountered: