Re: [Duplicity-talk] After full backup to S3, can I move older files to Glacier?

[edgar . soldin]

duplicity needs manifest and signatures all the time but volumes only for 
restoring.

you can use --file-prefix, --file-prefix-manifest, --file-prefix-archive, 
--file-prefix-signature parameters together w/ S3 lifecycle rules to move only 
volumes to glacier.
the parameters were introduced especially for this use case.

this of course only works for a new backup chain as your old one was created 
w/o these parameters.

..ede/duply.net

On 12.02.2016 15:17, Fabian Stäber wrote:
> Hi,
> 
> there are a lot of mails on S3 Glacier in the archive, but I didn't find an 
> answer to my question:
> 
> I back up to Amazon S3, using '--full-if-older-than 7D'. The S3 files are 
> moved to Glacier after 10 days.
> So I thought I could always restore the latest backup from S3 directly, and 
> Glacier would only be needed only in case I need an older backup.
> 
> However, when I run 'duplicity list-current-files s3://...', duplicity says
> 
>     Synchronizing remote metadata to local cache...
> 
> and downloads old 'duplicity-full-signatures...sigtar.gpg' files from 
> Glacier. I also tried the "--time now" option, but still old files are loaded 
> from Glacier.
> 
> How can I tell duplicity to use only files since the last full backup and not 
> to download files that are older than the last full backup?
> 
> Thanks a lot for your help
> Fabian
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>