Enabling incremental snapshot backups

When incremental snapshot backups are enabled (disabled by default), DataStax Enterprise hard-links each memtable-flushed SSTable to a backups directory under the keyspace data directory. This allows storing backups offsite without transferring entire snapshots. Also, incremental backups combined with snapshots provide a dependable, up-to-date backup mechanism. Compacted SSTables do not create hard links in /backups because these SSTables do not contain any data that has not already been linked. A snapshot at a point in time, plus all incremental backups and commit logs since that time form a compete backup.

As with snapshots, DataStax Enterprise does not automatically clear incremental backup files. DataStax recommends setting up a process to clear incremental backup hard links each time a new snapshot is created.

Procedure

  1. Edit the cassandra.yaml configuration file on each node in the cluster and change the value of incremental_backups to true.

  2. Restart each node to recognize the change.

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, 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. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000, info@datastax.com