Re: [Duplicity-talk] Moving old sets to cold storage (listing files to be deleted)

[edgar . soldin]

On 15.04.2016 12:00, Ladislav Laska wrote:
>> hmm, you are actually right. they are not listed, not sure if they ever were 
>> or this is a doc error. can you please file a ticket on launchpad for this?
> 
> Sure.

thanks

>> anyway - sorting out backup chains on the backend is easy, simply have a 
>> look! the files have timespans in their filename. 
>> a chain consists of a full followed by incrementals. 
>> a backup consists of a sig, manifest and volumes if there was data to backup.
> 
> Yeah, my set has 11k volumes and I was kind of hoping to find a reliable way 
> to
> do it.
> 
> I can easily move the full backup, but the incrementals always have dates of 
> the
> incrementals they are based upon. I want to avoid having to parse dates in the
> files (I'm just too lazy).

how about just sorting the file list alphabetically and then selecting the 
first file with full in the name (memorizing the timestamp of it) and keep 
selecting until the next file with a different full timestamp, excluding it.
 
> For now, I'll try to use filesystem date and hope it's accruate. Is there any
> option to verify if the set is complete and no volume is missing, besides
> restoring the whole set?
> 

you could locally, or wherever verify the chain. that's a restore file by file 
and compare with a checksum. it obviously only checks files existing at that 
point of time of course, meaning files flagged as deleted before are not 
checked.
but as a basic check that should suffice, as it would throw up on corrupt or 
missing volumes/files.

..ede/duply.net