[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] Deletion
From: |
edgar . soldin |
Subject: |
Re: [Duplicity-talk] Deletion |
Date: |
Fri, 24 Jan 2020 11:02:07 +0100 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 |
hi Foust,
On 24.01.2020 05:12, Fogust via Duplicity-talk wrote:
> I'm wondering how this scenario works:
>
> Let's say I use Duplicity for incremental, daily backups (the default
> being 200MB parts). I don't use any deletion scheme on a day-to-day
> basis. Every six months, I want to delete redundant data that is older
> than one year.
sounds like you never started another backup chain. hence your recent backups
depend on the old ones probably dating back into your deletion time frame.
> I'm expecting it to keep adding files until I reach the "cleanup" stage
> (twice per year). At that point, it should remove old data that isn't
> relevant anymore (deleted or changed). Since there are volumes, I
> imagine some might be deleted and others, updated (or deleted and
> reconstructed).
>
> Does this approach make sense with Duplicity? Am I on the right path?
duplicity treats backend as dumb file storage. it merely writes or reads data
from there. and because there is not target based duplicity a "reconstruction"
approach would need to re-transfer the whole data.
that is in turn equal to a simple new full which is the suggested methodology
here. simply use '--full-if-older-than 6M' during backup and you will end up
with a new independent chain every 6 months that can be safely discarded if not
needed anymore.
personally i keep monthly chains* and verify after every backup, just to be
sure.
*if one volume gets corrupted the whole chain might not be restorable by
default means, so regular full backups are advised.
..ede/duply.net