Re: [Duplicity-talk] mixed storage classes on S3

[edgar . soldin]

hey Hamish,

On 08.08.2022 07:30, hamish-duplicity--- via Duplicity-talk wrote:
> I am backing up to S3, and I set --s3-use-ia to set the storage class. I am 
> also using an S3 life cycle rule to transition the files to Glacier (flexible 
> retrieval) after 120 days.
>
> I think it would be useful to keep the metadata (manifest and signatures) in a 
> different class than the data, so that I can purge my local cache of the 
> metadata but get it back more readily if needed.

according to the source
 
https://gitlab.com/duplicity/duplicity/-/blob/main/duplicity/backends/s3_boto3_backend.py#L117-131
you can set multiple `--s3-use-` options.

manifests currently will never use glacier, glacier_ir, deep_archive but use 
the other given class instead. eg.
 --s3-use-ia --s3-use-glacier
would put all files up as class glacier except the manifests which will be 
saved as standard_ia .
  
> Unfortunately the S3 life cycle rules don't let you match by filename patterns, 
> so the only way to do this is to add tags to the files (either when uploaded, 
> or later, possibly with a lambda), or by setting the storage class differently 
> on the files when they are uploaded. Although then the data would go straight 
> to glacier rather than waiting 120 days.
>
>
> Would anyone have any suggestions on this?

afaiu others use the `--file-prefix-*` options for this as S3 is able to work 
with those.

..sunny regards ede