Tzach Livyatan

> If we expose the new options, users will start to use. It is confusing to set values differently for vnode or tablet tables. The reality is these are two...

> To address this, we would need to make the encryption keys multi-regional to facilitate the restoration process in such scenarios. Agree, but how this is a Scylla Manager issue...

@Michal-Leszczynski, to summarize, we have two tracks for fixing this issue in Scylla Manager - Short term: for 5.4 and 2024.1, disable Raft on cluster init, restore it, and then...

A new API option "small_table_optimization" Manager should set this value to true for all system tables.

Yes. Its make sense to write such operations to log, similar to Scylla Enterprise audit to syslog option. No need for an audit table.

We need to explain what is a broken restore, and how when can identify it.

Is this the revert a of [Manager 3.2 update](https://forum.scylladb.com/t/release-scylla-manager-3-2-0/815) ? > This release changes the parallelism and order of the repair job for better performance and stability. The following changes...

> As described in [SM docs](https://manager.docs.scylladb.com/stable/sctool/task.html#show-properties), --show-properties displays only the flags deliberately set by the user. Example: It's better UX to show *all* the parameters. It's hard for a user...

Good idea. Lets start with a quick PoC, even out side the Manager (just with rclone) to understand the impact on stored sstable size, time it taks to upload/download a...

Note that we are also building native S3 access in the Scylla core https://github.com/scylladb/scylladb/issues?q=is%3Aopen+is%3Aissue+label%3A%22object+storage%22 which can eventually replace the Manager agent upload function.