Re: [Duplicity-talk] cannot remove older backup

[edgar . soldin]

On 12.05.2017 14:24, John Covici wrote:
> No one told me I had to do that.  

well, now you know.

>How can I fix?  

move the new chain manually into a new folder on the backend. the file dates 
and names should help to determine, which belong to the new chain.

alternatively remove all par2 files and use the backend w/o the par2 wrapper.

alternatively make a new par2+azure:// full into a new folder.

>Without par2, I did
> this successfully already.

did you try 'remove-all-but-n-full' using the par2+azure:// backend?

..ede/duply.net

> 
> On Fri, 12 May 2017 08:02:40 -0400,
> edgar.soldin--- via Duplicity-talk wrote:
>>
>> John,
>>
>> you should have really backed up into a new backend folder ;) as you are now 
>> mixing backends within one target
>>
>> On 12.05.2017 13:59, John Covici via Duplicity-talk wrote:
>>> /usr/bin/duplicity remove-all-but-n-full 1 --force -v info --volsize 300 
>>> --gpg-options --pinentry-mode loopback --exclude-filelist 
>>> /etc/azure_excludes.txt --name backup_linux --encrypt-key address@hidden 
>>> --asynchronous-upload azure://linux
>>
>>
>> anyway, did you try 
>>
>> /usr/bin/duplicity remove-all-but-n-full 1 ... par2+azure://linux
>>
>> ?
>>
>> ..ede
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>