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

sync strategy #30

Closed
cgfrosty opened this issue Mar 21, 2013 · 9 comments
Closed

sync strategy #30

cgfrosty opened this issue Mar 21, 2013 · 9 comments
Milestone

Comments

@cgfrosty
Copy link

Hi,

We are very happy with your script. We have just 1 question.

Is it possible to delete file in vault in the process of synchronization when this file was deleted in source folder? Our inventory become very large.

Or we should delete all files in vault sometimes and do new sync?

Thank you!

Alex

@vsespb
Copy link
Owner

vsespb commented Mar 21, 2013

Hello.
Currently sync syncs only new files. Syncing modified files and propagating deletions is a important missing feature.
(I've just added this to to list of important missing features in README)

Implementing this is probably highest priority now, so should be done soon (however I cannot tell when exactly).
I will leave this ticket open until this done.

@cgfrosty
Copy link
Author

Thank you very much! We start waiting. :)

@bovnet
Copy link

bovnet commented Mar 21, 2013

+1

-------Original Message-------

From: cgfrosty

Date: 21/03/2013 07:02:20

To: vsespb/mt-aws-glacier

Subject: Re: [mt-aws-glacier] sync strategy (#30)

Thank you very much! We start waiting. :)

Reply to this email directly or view it on GitHub.

@jondavidjohn
Copy link

👍

@Kitof
Copy link

Kitof commented Mar 26, 2013

+1 I need this ! Thanks ;)

@chrisgahlert
Copy link

👍 as well.

Please keep in mind that a point in time recovery would also be very nice. I mean that when a file gets deleted locally it should not (immediately) be deleted at the remote end.

Anyway: Thanks for the awesome work so far!!

@vsespb
Copy link
Owner

vsespb commented Apr 3, 2013

I mean that when a file gets deleted locally it should not (immediately) be deleted at the remote end.
yes, this will be done some day too. (at least because Amazon Glacier has additional fee for early deletion)

Please keep in mind that a point in time recovery would also be very nice.
Planning this too, but lower priority

@vsespb
Copy link
Owner

vsespb commented Jul 9, 2013

Syncing modified files and propagating deletions done in 0.971beta. sync command behaviour documented. (see ChangeLog).

Thus I am closing this issue. But I am opening two new:

I mean that when a file gets deleted locally it should not (immediately) be deleted at the remote end.

#40

Please keep in mind that a point in time recovery would also be very nice.

#39

You can subscribe to these issues if you're waiting for such functionality.

@vsespb vsespb closed this as completed Jul 9, 2013
@chrisgahlert
Copy link

Thanks & good work!!!

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

6 participants