Lifecycle Management switches on provider site

General Topics
1

Hello everyone,

according to the instructions, it is recommended to use the S3 provider’s lifecycle Management (Ransomware Protection | Kopia).

I understand the requirement to mean that noncurrent versions should be automatically deleted after x days (capacity management): For the sake of simplicity, it is recommended to enter the same time as the retention time is set in Kopia. So far so good.

But I still stumbled across the “Removing expired delete markers” switch on S3 Provider site.

Is this switch relevant?

An object gets this status (expired delete markers) when it has been deleted and there are no more versions (if I understand correctly).

Does the S3 provider also have to clean up here, or can Kopia take care of that?

There is also the “cleanup of multipart objects” switch on provider site.

Kopia should recognize where the restart point is in the event of an interruption. So no S3 provider setting should be carried out - I think.

It can therefore probably be assumed that only the switch “delete previous versions after x days” is relevant…

Question is regarding all compatible cloud storage providers.

Thank you

2

Which S3 provider are you talking about?

Mine does not have such settings and I can only control rules for current and older versions. So it is not the same for all.

In general everything not current has to be managed by your lifecycle rules. Kopia does not touch it. Retention time in kopia is used only for setting retention of new objects and extending retention of other current objects.

3

The question was more general in nature, but I saw the settings at AWS.

Maybe I would then have to clarify the question of whether Kopia leaves orphaned chunk files behind, for example after deleting data from the source and expiring the retention period. I haven’t really looked under the hood that closely yet.

I’ll see if I can test that.

4

Kopia just deletes a file from repo - what is left behind and how it is managed is up to lifecycle rules on S3 side.