[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] old backups are not deleted
|
From: |
edgar . soldin |
|
Subject: |
Re: [Duplicity-talk] old backups are not deleted |
|
Date: |
Tue, 7 Mar 2017 15:45:43 +0100 |
|
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 |
please don't top post, when the answer was below ;)..
ok, so you have weekly chains. looks good to me. the files you mentioned do not
seem to exist any more.
when you did
duplicity remove-older-than 2M ..
before you probably ended up with a time before
Tue Feb 7 22:05:24 2017
so duplicity assumed you wanted to keep the chain before that as well.
why don't you go the easy route and do (from the manpage)
"
remove-all-but-n-full <count> [--force] <url>
Delete all backups sets that are older than the count:th last full backup
(in other words, keep the last count full backups and associated incremental
sets). count must be larger than zero. A value of 1 means that only the single
most recent backup chain will be kept. Note that --force will be needed to
delete the files instead of just listing them.
"
you probably want to keep 4 fulls (chains).. ede/duply.net
On 07.03.2017 15:31, Fazekas László via Duplicity-talk wrote:
> yes, this is my collection status:
>
> duplicity collection-status s3://...
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup date: Wed Mar 1 23:43:34 2017
> Collection Status
> -----------------
> Connecting with backend: BackendWrapper
> Archive dir: /root/.cache/duplicity/15cdc29d7e7bb895d21ee48765caa257
>
> Found 3 secondary backup chains.
> Secondary chain 1 of 3:
> -------------------------
> Chain start time: Tue Feb 7 22:05:24 2017
> Chain end time: Mon Feb 13 23:18:53 2017
> Number of contained backup sets: 10
> Total number of contained volumes: 11
> Type of backup set: Time: Num volumes:
> Full Tue Feb 7 22:05:24 2017 2
> Incremental Tue Feb 7 23:25:25 2017 1
> Incremental Wed Feb 8 00:19:05 2017 1
> Incremental Wed Feb 8 23:18:59 2017 1
> Incremental Thu Feb 9 22:18:45 2017 1
> Incremental Thu Feb 9 23:18:32 2017 1
> Incremental Fri Feb 10 23:18:28 2017 1
> Incremental Sat Feb 11 23:18:45 2017 1
> Incremental Sun Feb 12 23:18:50 2017 1
> Incremental Mon Feb 13 23:18:53 2017 1
> -------------------------
>
> Secondary chain 2 of 3:
> -------------------------
> Chain start time: Tue Feb 14 23:18:46 2017
> Chain end time: Mon Feb 20 23:42:33 2017
> Number of contained backup sets: 7
> Total number of contained volumes: 8
> Type of backup set: Time: Num volumes:
> Full Tue Feb 14 23:18:46 2017 2
> Incremental Wed Feb 15 23:18:51 2017 1
> Incremental Thu Feb 16 23:18:51 2017 1
> Incremental Fri Feb 17 23:18:47 2017 1
> Incremental Sat Feb 18 22:46:32 2017 1
> Incremental Sun Feb 19 23:40:43 2017 1
> Incremental Mon Feb 20 23:42:33 2017 1
> -------------------------
>
> Secondary chain 3 of 3:
> -------------------------
> Chain start time: Tue Feb 21 23:43:20 2017
> Chain end time: Tue Feb 28 23:43:06 2017
> Number of contained backup sets: 8
> Total number of contained volumes: 9
> Type of backup set: Time: Num volumes:
> Full Tue Feb 21 23:43:20 2017 2
> Incremental Wed Feb 22 23:42:25 2017 1
> Incremental Thu Feb 23 23:45:26 2017 1
> Incremental Fri Feb 24 23:46:46 2017 1
> Incremental Sun Feb 26 00:12:38 2017 1
> Incremental Sun Feb 26 23:40:43 2017 1
> Incremental Mon Feb 27 23:43:57 2017 1
> Incremental Tue Feb 28 23:43:06 2017 1
> -------------------------
>
>
> Found primary backup chain with matching signature chain:
> -------------------------
> Chain start time: Wed Mar 1 23:43:34 2017
> Chain end time: Mon Mar 6 23:45:12 2017
> Number of contained backup sets: 6
> Total number of contained volumes: 7
> Type of backup set: Time: Num volumes:
> Full Wed Mar 1 23:43:34 2017 2
> Incremental Thu Mar 2 23:44:23 2017 1
> Incremental Fri Mar 3 23:44:07 2017 1
> Incremental Sat Mar 4 23:40:06 2017 1
> Incremental Sun Mar 5 23:34:41 2017 1
> Incremental Mon Mar 6 23:45:12 2017 1
> -------------------------
> No orphaned or incomplete backup sets found.
>
> 2017-03-07 14:31 keltezéssel, edgar.soldin--- via Duplicity-talk írta:
>> On 06.03.2017 22:46, Fazekas László via Duplicity-talk wrote:
>>> Hi!
>>>
>>> I've a duplicity backup script, something like this:
>>>
>>> ...
>>> duplicity --no-encryption --full-if-older-than 1W /var/backups/hotcopy-dup
>>> s3://...
>>> ...
>>> duplicity remove-older-than 2M --force s3://...
>>>
>>> The second part should delete my old backups, but it doesn't. It says:
>>>
>>> Last full backup date: Sat Feb 25 22:17:37 2017
>>> There are backup set(s) at time(s):
>>> Mon Dec 26 23:59:29 2016
>>> Tue Dec 27 00:00:56 2016
>>> Tue Dec 27 01:17:03 2016
>>> Wed Dec 28 01:17:02 2016
>>> Wed Dec 28 17:54:00 2016
>>> Wed Dec 28 19:25:45 2016
>>> Wed Dec 28 22:17:02 2016
>>> Thu Dec 29 22:17:03 2016
>>> Fri Dec 30 22:17:02 2016
>>> Sat Dec 31 22:17:02 2016
>>> Sun Jan 1 22:17:03 2017
>>> Mon Jan 2 22:17:02 2017
>>> Tue Jan 3 22:17:03 2017
>>> Wed Jan 4 22:17:02 2017
>>> Thu Jan 5 22:17:03 2017
>>> Which can't be deleted because newer sets depend on them.
>>> No old backup sets found, nothing deleted.
>>>
>>> Why newer sets depends on backups before 2017.02.25, which is the last full
>>> backup date?
>>>
>>> Thank you.
>>>
>> can you send a collection-status? ..ede/duply.net
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>
>
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk