cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Durity, Sean R" <>
Subject RE: AWS Cassandra backup/Restore tools
Date Tue, 12 Sep 2017 14:27:59 GMT
Datos IO has a backup/restore product for Cassandra that another team here has used successfully.
It solves many of the problems inherent with sstable captures. Without something like it,
restores are a nightmare with any volume of data. The downtime required and the loss of data
since the snapshot are usually not worth it.

Sean Durity

From: Alexander Dejanovski []
Sent: Friday, May 12, 2017 12:14 PM
To: Manikandan Srinivasan <>; Nitan Kainth <>
Cc: Blake Eggleston <>; cass savy <>;
Subject: Re: AWS Cassandra backup/Restore tools


here are the main techniques that I know of to perform backups for Cassandra :

  *   Tablesnap (<>)
: performs continuous backups on S3. Comes with tableslurp to restore backups (one table at
a time only) and tablechop to delete outdated sstables from S3.
  *   incremental backup : activate it in the cassandra.yaml file and it will create snapshots
for all newly flushed SSTables. It's up to you to move the snapshots off-node and delete them.
I don't really like that technique since it creates a lot of small sstables that eventually
contain a lot of outdated data. Upon restore you'll have to wait until compaction catches
up on compacting all the history (which could take a while and use a lot of power). Your backups
could also grow indefinitely with this technique since there's no compaction, so no purge.
You'll have to build the restore script/procedure.
  *   scheduled snapshots : you perform full snapshots by yourself and move them off node.
You'll have to build the restore script/procedure.
  *   EBS snapshots : probably the easiest way to perform backups if you are using M4/R4 instances
on AWS.


On Thu, May 11, 2017 at 11:01 PM Manikandan Srinivasan <<>>
Blake is correct. OpsCenter 6.0 and up doesn't work with OSS C*. @Nitan: We have made some
substantial changes to the Opscenter 6.1 backup service, specifically when it comes to S3
backups. Having said this, I am not going to be sale-sy here. If folks need some help or need
more clarity to know more about these improvements, please send me an email directly:<>


On Thu, May 11, 2017 at 1:54 PM, Nitan Kainth <<>>
Also , Opscenter backup/restore does not work for large databases

Sent from my iPhone

On May 11, 2017, at 3:41 PM, Blake Eggleston <<>>
OpsCenter 6.0 and up don't work with Cassandra.

On May 11, 2017 at 12:31:08 PM, cass savy (<>)
AWS Backup/Restore process/tools for C*/DSE C*:

Has anyone used Opscenter 6.1 backup tool to backup/restore data for larger datasets online

If yes, did you run into issues using that tool to backup/restore data in PROD that caused
any performance or any other impact to the cluster?

If no, what are other tools that people have used or recommended for backup and restore of
Cassandra keyspaces?

Please advice.


Manikandan Srinivasan

Director, Product Management| +1.408.887.3686<tel:%2B1.408.887.3686> |<>

[Image removed by sender. linkedin.png]<>[Image
removed by sender. facebook.png]<>[Image
removed by sender. twitter.png]<>[Image
removed by sender. g+.png]<>[Image
removed by sender.]<>[Image
removed by sender.]

Alexander Dejanovski

Apache Cassandra Consulting<>


The information in this Internet Email is confidential and may be legally privileged. It is
intended solely for the addressee. Access to this Email by anyone else is unauthorized. If
you are not the intended recipient, any disclosure, copying, distribution or any action taken
or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed
to our clients any opinions or advice contained in this Email are subject to the terms and
conditions expressed in any applicable governing The Home Depot terms of business or client
engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy
and content of this attachment and for any damages or losses arising from any inaccuracies,
errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature,
which may be contained in this attachment and shall not be liable for direct, indirect, consequential
or special damages in connection with this e-mail message or its attachment.
View raw message