Hi everyone, I would like to discuss the possibility of having a built-in backup and restore mechanism in Cassandra, including incremental backups and support for external object storage such as S3. The main goal would be to provide a supported solution while keeping the implementation provider-agnostic and avoiding unnecessary operational overhead.
I initially discussed this on Slack and was pointed to CEP-36 and the previous discussions around external storage and snapshots. We also discussed whether S3 would be too provider-specific, and whether Cassandra Sidecar could be part of the solution. My concern with Sidecar is that introducing another component would increase the operational footprint, which goes against one of the goals of this work. I also have a small PoC on top of trunk exploring some of these ideas. I'd be interested in hearing other opinions and any previous work I should look at. If there is interest in pursuing this, would a draft CEP be a useful next step so we can start working on the design in parallel? Link of the first slack discussion about this topic: https://the-asf.slack.com/archives/CK23JSY2K/p1789021792614639 Thanks, Victor Cavichioli
