Skip to content
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

Closed
peter-dolkens opened this issue Sep 1, 2016 · 8 comments
Closed

Feature Request: Versioning / Conflict resolution #670

peter-dolkens opened this issue Sep 1, 2016 · 8 comments

Comments

@peter-dolkens
Copy link

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:

  1. Upload new file as [yyyyMMddHHmm]-[filehash].tmp
  2. Move existing file to .archive/[yyyyMMddHHmm]-filename.ext
  3. Rename temporary file to filename.ext

This provides simple version history for the remote files.

@ermint
Copy link

ermint commented Sep 4, 2016

Some backends support this transparently. See versioning in S3. I think google cloud supports similar.

@peter-dolkens
Copy link
Author

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

On 4 Sep 2016, at 10:11, ermint notifications@github.com wrote:

Some backends support this transparently. See versioning in S3. I think google cloud supports similar.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@leocrawford
Copy link

Is this a dupe of #18?

@peter-dolkens
Copy link
Author

@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.

@leocrawford
Copy link

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

@ncw
Copy link
Member

ncw commented Sep 19, 2016

My plan for this is to implement #98 then implement a seperate higher level rclone backup command which would do a backup with ability to see previous backup snapshots up to some limit.

Each time you ran the rclone backup command you'd get a new snapshot.

I will spec it out a bit later

@ncw ncw added the enhancement label Jan 9, 2017
@MourIdri
Copy link

MourIdri commented Oct 5, 2017

@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.
Thanks for this is is Awesome !

@ncw
Copy link
Member

ncw commented Dec 14, 2017

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.

@ncw ncw closed this as completed Dec 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants