Israel Fruchter

I think it's not enough for the restore nemesis, since all of the backups were created with older scylla and older manager. someone would need to recreate the backend with...

> @mikliapko - is the original flow covered in one of the SM specific jobs? > If so IMO the nemesis should use the latest scylla and SM releases. >...

> > @mikliapko - is the original flow covered in one of the SM specific jobs? If so IMO the nemesis should use the latest scylla and SM releases. @fruch...

> @roydahan @fruch @ShlomiBalalis I'm about to prepare the new snapshots for restoration instead of [current](https://github.com/scylladb/scylla-cluster-tests/blob/master/defaults/manager_persistent_snapshots.yaml). Just wondering how the previous snapshots were prepared. Do we have some auxiliary scripts,...

> So, I've updated snapshots and re-executed the `longevity-twcs-3h-test` test. It did restore schema and data operations successfully but failed on running verification stress: > > ``` > 2024-08-08 13:23:21.822:...

> @aleksbykov The issue reproduced in 2024.1.9 - [https://argus.scylladb.com/test/c64d7261-b3df-451a-9d66-b8d6acb4cb35/runs?additionalRuns[]=227e1a0d-6187-46d7-9569-02e21b769fad](https://argus.scylladb.com/test/c64d7261-b3df-451a-9d66-b8d6acb4cb35/runs?additionalRuns%5B%5D=227e1a0d-6187-46d7-9569-02e21b769fad). This fix was not backported - was it done intentionally maybe? Or we can follow up on it now? we can...

> See this is ignoring AZ setting and it creates CR after spinning sct-runner so possibly runner is in different AZ. > Do we accept this caveat or I should...

@vponomaryov @juliayakovlev can you give @soyacz a hand in review this one ?

@soyacz can you put here a link to results of this PR runs ?

@soyacz also we would need a PR with those changes also for master