[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] incremental backups only?
From: |
edgar . soldin |
Subject: |
Re: [Duplicity-talk] incremental backups only? |
Date: |
Tue, 21 Mar 2017 12:58:57 +0100 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
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.
..ede/duply.net
Re: [Duplicity-talk] incremental backups only?, Ed Blackman, 2017/03/27