S3 Repository sealed?

[Daniel2]

Some weeks ago I added an S3-compatible repository that makes objects immutable, and added it to the capacity tier of our SOBR.

Today I noticed by accident, that the S3 repository is set to "Seal Extend". I searched the system history for "Seal" and could not find one entry that indicated it was sealed manually.

Now I'm wondering if Veeam set the extend to seal due to switching on or off a particular configuration in the Repository, SOBR or a backup job that references it, or if it was me or a colleague who sealed the extent by accident.

Could you maybe tell me, if sealing is a purely manual operation, or whether there is a certain configuration that does enforces a repository to become sealed?

[veremin]

It's pure manual operation that does not get triggered by other product activity - so it's been a human factor most likely

[Daniel2]

Great, thanks!