duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] Duplicity wiped out my server


From: Mikko Ohtamaa
Subject: Re: [Duplicity-talk] Duplicity wiped out my server
Date: Wed, 6 May 2015 16:11:38 +0300



I'm fully aware of the fact that this might not be a "bug" per se, however, I maintain that this is poor UX design (or, say, command-line design).

The command I tried to use was more or less like this:

duplicity --file-to-restore www/foobar.com/blah.html s3://amazon.com/foobar /

It then warned me that the destination exists (or something), and that it "won't overwrite" unless I specify --force.

Well, I DID specify --force and repeated, because for the life of me I didn't expect it to wipe out the destination path for restoring a single file (--file-to-restore).

I noticed what it was doing when it was far too late -- errors about /proc/ files and "permission denied".

I think I now understand WHY it did that, however, I still don't think it's right. duplicity works totally differently to any other tool I know (rsync, tar), while it serves a similar purpose. This is dangerous. I think anyone with experience with tar or rsync, reading the above command line, would think: "OK, it will restored the file www/foobar.com/blah.html, creating parent folders as necessary, and will do this relative to the path '/'". Again, ESPECIALLY because an option named "file-to-restore" is given, I guess nobody would expect it to delete ANYTHING. EVER.

Thanks! This explains in quite a detail how it happened.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]