|
From: | Manuel Morales |
Subject: | Re: [Duplicity-talk] Minimizing risk on incremental |
Date: | Sat, 22 Apr 2017 16:25:23 -0400 |
User-agent: | Microsoft-MacOutlook/f.17.0.160611 |
That’s a good ideal also, but like you said, it will require more space. Duplicity seems to be great, in the traditional backup sense, the problem here is that IM using ZFS snapshots, which basically provide the same, but avoiding the broken chain issues. In my case then I don’t know, if I use duplicity I get the nice encryption but I introduce a backup chain in my logic, and if I don’t use, then the data inside my snapshots will not be encrypted. Is there any way to disable the chain in duplicity and have it behave just like rsync but just adding encryption? From: Mark Grandi <address@hidden> You can use the par2 wrapper backend that takes a little more space but provides redundancy if one of the chain files gets corrupted somehow (flips a bit...Solar radiation? Bad disk?) ~mark On Apr 22, 2017 6:15 AM, "Manuel Morales via Duplicity-talk" <address@hidden> wrote:
|
[Prev in Thread] | Current Thread | [Next in Thread] |