Eugene Klimov

Hello @manjuraj what status of this pull request, it will be merged?

no this is a different issue, but could be related usign {uuid} in replication path always bad idea from my perspective do you mean restoring `ReplicatedMergeTree` on the different replicas...

you also could try to use ``` general: restore_metadata_on_cluster: "{cluster}" ``` after that ReplicatedMergeTree will create on cluster with the same UUID > it didn't use the uuid of the...

if you will use restore_metadata_on_cluster in this case you just need execute restore --schema only in one replica in whole cluster and use restore --data only in first replica in...

Which `clickhouse-backup` version do you use?

could you upgrade to 2.4.35 ?

Need more logs from `clickhouse-backup` container to understand what's wrong

This is a different question, provide more context Is your clickhouse-backup configuration defined as a separate `ConfigMap`? Do you use `clickhouse-operator` or install `clickhouse-server` some different way? By default, kubernetes...

How did you change configuration in this case? Did you use `env` section? could yuou share `kind: ClickHouseInstallation` manifest without sensitive credentials?

Sorry, I close issue because you didn't answer to my questions and didn't provide more context Please don't hesitate to reopen the issue, if it is still relevant to you....