About the DSE Backup and Restore Service

The DSE Backup and Restore Service enables cluster-wide backup and restore and lets you easily:

  • Create flexible local or cloud-based backup stores

  • Create backup configurations that enable you to schedule automatic keyspace backups at any frequency you require

  • Configure detailed backup retention policies depending on your needs

  • Handle all backup tasks from a single node using a simple set of CQL commands

  • Flexibly restore backups both to a current cluster as well as new clusters, at either the keyspace or table level

Easy configuration and administration

Configuring the DSE Backup and Restore Service requires only three steps:

  1. Change the required cassandra.yaml settings on all nodes in your cluster and restart the node to enable the Backup and Restore Service. For details, see Enabling and configuring the DSE Backup and Restore Service.

  2. Create a backup store to hold your data. For details, see Creating and managing backup stores.

  3. Create a backup configuration that determines what keyspace is backed up, where it’s stored and how often the backup should run. For details, see Creating and managing backup configurations.

Once you’ve got the DSE Backup and Restore Service configured and running, your backups will run automatically using the schedule you’ve determined, with no intervention required. You can then manage backups from the backup administration node using a comprehensive set of built in CQL commands. For details, see Backup and Restore Service CQL Command Reference.

Local, NFS and cloud-based backup stores

The DSE Backup and Restore Service gives you the choice of storing backups in fault-tolerant cloud storage systems as well as on either local node storage or NFS mounts. Both Google Cloud and Amazon S3 as well as S3 compatible services are supported. If you wish to keep your data within your organization, you can also choose to back up to local storage on the backup administration node itself, or a shared NFS mount. In addition, for further redundancy, you can back up data to multiple backup stores at once. For details, see Creating and managing backup configurations.

Comprehensive backup configuration and retention policies

You can create backup configurations that run automatic backups at any period you require, using standard cron specifications, specifying whether you require data recoverable to the minute or the month. For details, see Creating and managing backup configurations.

In addition, using only two cassandra.yaml configuration parameters, you can create a retention policy to determine how many backups you want to store, and for how long they should be stored. You can store any number of backups for any length of time you require, for instance a minimum of three backups available within a week. For details, see Customize backup retention policy.

Restore keyspaces and tables to existing and new clusters

Once you’ve configured the Backup and Restore Service and created backups, you can restore either complete keyspaces, or a selection of tables within the backed up keyspace. You can restore backed up keyspace data into a new keyspace, and you can also reference backup store configurations from one cluster’s backup store to restore data into another cluster. For details, see Restoring backups.

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