Re: [Duplicity-talk] incremental backups only?

[edgar . soldin]

On 21.03.2017 18:36, John Covici wrote:
> On Tue, 21 Mar 2017 07:58:57 -0400,
> edgar.soldin--- via Duplicity-talk wrote:
>>
>> On 21.03.2017 08:00, Raphael Bauduin via Duplicity-talk wrote:
>>>
>>>
>>> On Mon, Mar 20, 2017 at 8:35 PM, Kenneth Loafman <address@hidden 
>>> <mailto:address@hidden>> wrote:
>>>
>>>     Hi,
>>>
>>>     Long strings of incremental backups are subject to failure if one of 
>>> the incrementals is corrupted.  I normally do full backups once a week and 
>>> incrementals on the other days.  You might stretch that to two or three 
>>> weeks, depending on the reliability of your storage provider, but I would 
>>> strongly suggest at least two full, verified, backups at all times if you 
>>> go the long-string route.  You can always remove the incrementals once the 
>>> next backup and verification is done.
>>>
>>>
>>> OK, thanks
>>>
>>
>> Raph,
>>
>> you may mitigate volume corruption via the par2 backend wrapper, but that of 
>> course adds parity data, which you might not want if you are constrained for 
>> space.
>
> Can you use this backend in connection with other backends?  I am
> currently using the azure back end, but if I could get parity that
> would be nice.
>

check the manpage
  http://duplicity.nongnu.org/duplicity.1.html#sect21

never used it myself, but supposedly it is working for some people.

..ede/duply.net