Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We currently have 12 nodes running in our Cassandra cluster. Ultimately even if a couple of the nodes go down, we're still up and running. The paranoia in me would like to do at least one backup a day and store it on Amazon S3. My question is the following:

When backing up Cassandra, is it sufficient to run the backup from one node, or do I have to run a backup script from each one of the 12 nodes and push its respective backup onto S3? If at one point a restore is required, do we have to backup from the individual nodes backup, or is there a way to "aggregate" the backups (assuming you need to take them from each node individually) into one large restore process?

Slightly confused by the documentation. Just want to get an efficient backup process rolling on my Cassandra cluster.

share|improve this question

You need to back each node up, unless every node stores 100% of the data, then you can back only one node up.

share|improve this answer

The easiest way to back up Cassandra is to back up each node. I've used tablesnap before to do this automatically and it's pretty good. There's also Priam from Netflix but I haven't tried it personally.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.