Can/Should you restore the `system` keyspaces in a Cassandra cluster? Taking this a step backwards, can/should you backup the `system` keyspaces in a Cassandra cluster?
Are there pros/cons to either approach?
Bringing together the Apache Cassandra experts from the community and DataStax.
Want to learn? Have a question? Want to share your expertise? You are in the right place!
Not sure where to begin? Getting Started
There is a narrow use case for taking backups of system keyspaces.
Yes, you should perform regular backups of the system keyspaces but you should only ever restore them in the event of a complete server failure.
In most cases, system keyspaces contain information about the local node. They are not relevant if you are cloning application data to another cluster.
For most situations, it would be quicker to build a server from scratch and replace a node with the replace_address
flag (see Replacing a dead node) than it is to restore from backups but YMMV. Cheers!
5 People are following this question.
Can we restore a keyspace which contains a UDT to another keyspace?
Does a snapshot of keyspaces take a backup of user roles and permissions?
Does OpsCenter support restoring data to a different table than the source table?
Restoring archived commitlogs does not recover deleted rows
How can I backup JanusGraph data and restore it to a new node?
DataStax Enterprise is powered by the best distribution of Apache Cassandra ™
© 2022 DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.
Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.
Privacy Policy Terms of Use