|
From: | Jeffrey |
Subject: | Re: [Duplicity-talk] Question on dealing with Archives |
Date: | Wed, 7 Jun 2017 18:45:55 -0400 |
My knowledge is weak when it comes to server admin so without something like Duplicity I don't know how to make that happen.My point was that if you are not using any of the incremental features or the ability to restore at various points in time etc, you do not need duplicity at all and could just create a tar.gz as normal and upload it. Tar can even handle --exclude statements etc.
Hello Jeffrey,
On 07/06/17 18:16, Jeffrey wrote:
Aren't we all!Thanks Aaron,
I'm sure you are right, I'm trying to bend Duplicity to my needs.
My point was that if you are not using any of the incremental features or the ability to restore at various points in time etc, you do not need duplicity at all and could just create a tar.gz as normal and upload it. Tar can even handle --exclude statements etc."Alternatively, if you are just wanting a full backup that you can easily extract, is there a reason not to just do a compressed archive (e.g. a tar.gz)?"
-is there a way to set Duplicity to create and upload to S3 a simple compressed archive like a tar.gz? My apologies if I'm missing the obvious.
There is not a way to make duplicity create tar.gz files -- all those extra files and diffs you do not want are how we can do the efficient incremental versions. Unless you are using duplicity for an additional reason that I am missing. Why do you think you need duplicity?
As I say, if you only need one version and simplicity is key, I would just zip/tar.gz up the files and copy them onto Amazon or whatever.My goal is to keep things simple to deal with in the event of a problem. For example I often travel and it would love it if I could use any available device to log in to my S3 account and get usable files with what's available on the computer at hand. I'd need just a browser and FTP to be back up and running. Could be Windows, Mac, Chromebook or even a smartphone.
Not trying to dissuade you from using duplicity, but something else may fit this use case better.
Kind regards,
Aaron
[Prev in Thread] | Current Thread | [Next in Thread] |