Michal-Leszczynski

Ref for Scylla versions constraints: https://github.com/scylladb/scylla-enterprise/issues/4140#issuecomment-2095497858.

``` < t:2023-08-16 19:54:15,367 f:base.py l:142 c:RemoteLibSSH2CmdRunner p:DEBUG > Command "sudo sctool backup -c 4105638a-e5a7-4c68-b8c2-614904a59131 --keyspace keyspace1 --location s3:manager-backup-tests-us-east-1 --cron '56 19 * * *' " finished with status 0...

What is interesting here, is that the backup bucket contains two different clusters `4105638a-e5a7-4c68-b8c2-614904a59131`, `0fa19c7a-d21a-4bff-9f19-80c33dd2ae15` and both of them have a backup with the same snapshot tag `sm_20230816195600UTC`. This is...

@ShlomiBalalis ping

So from my perspective, this looks like there were concurrent test execution or something similar. @ShlomiBalalis was this issue ever reproduced? If not, could we rerun it and see if...

@ShlomiBalalis ping

@mikliapko is this something that you could take care of? I mean investigating the reasons for two clusters being there.

Previously we were sending 1 range per request on our test env setup, now it goes to 10/17 depending on keyspace replication.

Note that this is `10% of replica set ranges`, so not `10% of all table ranges` as I though the latter could be too much and I didn't get which...

CC: @karol-kokoszka @vladzcloudius