Hi Petr,
>From the question, it looks like you are trying to find a shortcut to avoid
longer restore times without having data loss. The TLDR answer to your
question is that you cannot workaround by doing node level restore since
the corrupted data will eventually get propagated. But there are
Hi Petr,
If data corruption means accidental data deletions via Cassandra commands, you
have to restore entire cluster with latest snapshots. This may lead to data
loss as there may be valid updates after the snapshot was taken but before the
data deletion. Restoring single node with snapshot
You can have situations where rebuilding a node via streaming is painful
and slow (generally because there is something bad about the data model
like misused secondary indexes or massive partitions). Also, overstreaming
can mean you need more disk space to bootstrap a node than you’ll require
once
Hi.
I have a question about Cassandra backup-restore strategies.
As far as I understand Cassandra has been designed to survive hardware failures
by relying on data replication.
It seems like people still want backup/restore for case when somebody
accidentally deletes data or the data gets
