Julio López

@jkowalski It may be worth looking at the client - repo server path. This may be in the RPC handlers.

#1345

S3-compatible object locking relies on 2 main features to provide "immutability" and protect objects from deletion or corruption: (1) object _retention_ times; and (2) object _versioning_. When an object-locking bucket...

@drsound IIUC B2 offers a [S3-compatible interface](https://www.backblaze.com/b2/docs/s3_compatible_api.html). Presumably, the S3 implementation should work. It would require accessing the repo as if it were a S3 store. I don't have access...

> ... enough for small backups and perform some testing. Good to know, definitely helpful for testing.

According to the B2 documentation, it seems that B2's S3 API should provide all the functionality that kopia needs from the store via the S3 API. https://www.backblaze.com/b2/docs/s3_compatible_api.html Also, other folks...

No documentation yet, PRs are welcome. Here are the high-level steps at _the top of my head_. I hope this helps. ### Repo Setup 1. [Enable versioning on the bucket](https://docs.aws.amazon.com/AmazonS3/latest/userguide/manage-versioning-examples.html),...

> What I have been trying for the last week (not long enough to have fully tested) is backups every day at midnight with Kopia policy of 90 daily backups....

In AWS S3, it is possible to define a lifecycle policy that deletes the non-current blob version X days after the blob was deleted. Some details: - Suppose kopia writes...

- Create a bucket with object locking (for AWS S3 see https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock.html or the specific S3-provider documentation) - Set a default retention period for newly created blobs: `kopia repo set-parameters...