Michal-Leszczynski

right, @AdamStawarz ?

@ShlomiBalalis @tzach I think that during some meeting we agreed that user is responsible for providing the right schema and SM will not try to verify that (it will try...

This is a difficult question for me, because it's more about Scylla core than SM. (SM only delivers SSTables from backup but does not interpret them) From some experiments run...

@asias I believe that we cannot 100% trust the output of describe schema that is uploaded to backup. Here is a comment from backup procedure: ```go // Always backup system_schema....

What is a good place to store this information in documentation? I see three candidates: - [general sctool description](https://manager.docs.scylladb.com/stable/sctool/index.html) - new subsection in sctool like: Scylla Manager server restart -...

@tzach do you know how we should set those default values?

Actually, awaiting schema agreement is only possible when SM has cluster CQL credentials - so this idea is only feasible for this scenario. Unless we can require to always have...

Idea: what if we added something like `DESCRIBE SCHEMA` command to SM, so that user could run it to get a simple bash script that recreates all SM tasks? This...

> I'm not sure if I follow the idea. Could you please elaborate ? The example output of this command would be: ``` sctool backup -L s3:loc --cron @weekly --retention...

I suppose that we can put https://github.com/scylladb/scylla-manager/issues/3744 in 3.3.1 milestone. @karol-kokoszka what do you think?