Backup strategy

Hi , I'm from relational world recently started working on Cassandra. I'm just wondering what is backup best practices for DB around 100 Tb with multi DC setup. Thanks, Vasu

backup strategy

Hi - If we have a RF=2 in a 4 node cluster, how do we ensure that the backup taken is only for 1 copy of the data ? in other words, is it possible for us to take back-up only from 2 nodes and not all 4 and still have at least 1 copy of the data ? Thanks, Kanwar

Backup strategy

is to run backups against a replica that does not serve requests. Questions: 1. *Is it the right strategy? * 2. *if it is - how do I pull a replica out from serving requests ? * 3. *If not, what is the right backup strategy ?*

Backup Strategy

I got some very good advice on manual compaction so I thought I would throw out another question on raid/backup strategies for production clusters. We are debating going with raid 0 vs. raid 10 on our nodes for data storage. Currently all storage we use is raid 10 as drives always fail and raid 10

Re: Backup strategy

Hi Vasu, Planet Cassandra has a documentation page for basic info about migrating to cassandra from MySQL. What to expect and what not to. It can be found here . I had a look at this slide

Re: Backup strategy

Bhuvan, Thanks for the info but actually I'm not looking for migration strategy. just want to backup strategy and retention policy best practices Thanks, Vasu > On Jun 16, 2016, at 6:51 PM, Bhuvan Rawal wrote: > > Hi Vasu, > > Planet Cassandra has a documentation page

Re: Backup strategy

TB per node if data is not updated frequently. Regards, Bhuvan On Fri, Jun 17, 2016 at 4:31 AM, wrote: > Bhuvan, > > Thanks for the info but actually I'm not looking for migration strategy. > just want to backup strategy and retention policy best practices > > Thanks, >

Re: Backup strategy

Also if we talk about backup strategy for Cassandra Data then essentially there are couple of strategies that are adopted: 1. Incremental Backups. The old sstables will remain inside a backup directory and can be shipped to a storage location like AWS Glacier, etc. 2. Snapshotting : Hardlinks of

Re: Backup strategy

On Thu, Jun 16, 2016 at 7:30 PM, Bhuvan Rawal wrote: > 2. Snapshotting : Hardlinks of sstables will get created. This is a very > fast process and latest data is captured into sstables after flushing > memtables, snapshots will be created in snapshots directory. But snapshot > does not provide you

Re: Backup strategy

, Bhuvan Rawal wrote: > Also if we talk about backup strategy for Cassandra Data then essentially > there are couple of strategies that are adopted: > > 1. Incremental Backups. The old sstables will remain inside a backup > directory and can be shipped to a storage location like AWS Gl

Re: Backup strategy

Snapshot would flush your memtable to disk and you could stream your sstables out. Incremental backups would be the differences that have occurred since your last snapshot as far as I'm aware. Since it's reasonably unfeasible to constantly stream out full snapshots (depending on the density of yo

Optimal backup strategy

Hi, I was looking for the backup strategies of Cassandra. After some study I came to know that there are the following options: - Snapshot based backup - Incremental backups - Snapshot + incremental - Snapshot + commitlog archival - Snapshot + Incremental + commitlog Which is the

Re: backup strategy

Assuming you are using the SimpleStrategy or the NetworkTopologyStrategy and one rack per DC. If you backed up every 2nd node you would get one copy *IF* all nodes were consistent on disk. That can be a reasonably large if that you need to monitor. It's easier to back up all the nodes it will a

Re: Backup strategy

> particular time where we can schedule backups, periodically. > > My current thinking is to run backups against a replica that does not serve > requests. Questions: > > Is it the right strategy? > if it is - how do I pull a replica out from serving requests ? > If not, what is the right backup strategy ?

Re: Backup strategy

> serve > > requests. Questions: > > > > Is it the right strategy? > > if it is - how do I pull a replica out from serving requests ? > > If not, what is the right backup strategy ? >

Re: Backup strategy

On Tue, Nov 5, 2013 at 4:36 PM, Sridhar Chellappa wrote: > >1. *If not, what is the right backup strategy ?* > > You didn't specify, but it sounds like you are doing a snapshot and then a full offhost backup of the sstables? Perhaps instead of point in time full b

Re: Backup strategy

Yes. I am taking a Snapshot and then offloading the full data into S3. How will Table Snap help? On Wed, Nov 6, 2013 at 6:57 AM, Robert Coli wrote: > On Tue, Nov 5, 2013 at 4:36 PM, Sridhar Chellappa > wrote: > >> >>1. *If not, what is the right backup strateg

Re: Backup strategy

On Thu, Nov 7, 2013 at 6:28 AM, Sridhar Chellappa wrote: > Yes. I am taking a Snapshot and then offloading the full data into S3. > How will Table Snap help? > As I detailed in my previous mail : 1) incremental style backup, instead of snapshot + full 2) tracks meta information about backup set

Re: Backup strategy

Thanks for sharing tablesnap. It's just what I have been looking for. On Thu, Nov 7, 2013 at 5:10 PM, Robert Coli wrote: > On Thu, Nov 7, 2013 at 6:28 AM, Sridhar Chellappa > wrote: > >> Yes. I am taking a Snapshot and then offloading the full data into S3. >> How will Table Snap help? >> >

Re: Backup Strategy

On Tue, Nov 9, 2010 at 8:15 AM, Wayne wrote: > I got some very good advice on manual compaction so I thought I would throw > out another question on raid/backup strategies for production clusters. > > We are debating going with raid 0 vs. raid 10 on our nodes for data storage. > Currently all stor

Re: Backup Strategy

Thanks for the details. I think we were slowly starting to realize a similar pattern, but you definitely helped fill in the gaps: home brew rsync with lzop in the middle. We have raid1 system/commit log drives we are copying to once a day, and off cluster...maybe once a week. Thanks On Tue, Nov

Re: Backup Strategy

On 11/9/10 5:15 AM, Wayne wrote: We are trying to use snapshots etc. to back up the data but it is slow (hours) and slows down the entire node. The snapshot process (as I understand it, and with the caveat that this is the code path without JNA available) first flushes all memtables (this can

Re: Optimal backup strategy

Hi, TheLastPickle & Spotify have released Medusa as Cassandra Backup tool. See : https://thelastpickle.com/blog/2019/11/05/cassandra-medusa-backup-tool-is-open-source.html Hope this link will help you. Eric Le 27/11/2019 à 08:10, Adarsh Kumar a écrit : Hi, I was looking for the backup st

Re: Optimal backup strategy

For me, I think the last one : Snapshot + Incremental + commitlog is the most meaningful way to do backup and restore, when you make the data backup to some where else like AWS S3. - Snapshot based backup // for incremental data will not be backuped and may lose data when restore to the tim

Re: Optimal backup strategy

Thanks Guo and Eric for replying, I have some confusions about commit log backup: 1. commit log archival technique is ( https://support.datastax.com/hc/en-us/articles/115001593706-Manual-Backup-and-Restore-with-Point-in-time-and-table-level-restore- ) as good as an incremental backup, a

Re: Optimal backup strategy

for cassandra or datastax's documentation, commitlog's backup is not mentioned. only snapshot and incremental backup is described to do backup . Though commitlog's archive for keyspace/table is not support but commitlog' replay (though you must put log to commitlog_dir and restart the process) sup

Re: Optimal backup strategy

commitlog backup isn't usable in another machine. Backup solution depends on what you want to do: periodic backup or backup to restore on other machine? Periodic backup is combine of snapshot and incremental backup. Remove incremental backup after new snapshot. Take backup to restore on other machi

Re: Optimal backup strategy

Hossein is right , But for use , we restore to the same cassandra topology ,So it is usable to do replay .But when restore to the same machine it is also usable . Using sstableloader cost too much time and more storage(though will reduce after restored) Hossein Ghiyasi Mehr 于2019年11月28日周四 下午7:40

Re: Optimal backup strategy

Thanks Ahu and Hussein, So my understanding is: 1. Commit log backup is not documented for Apache Cassandra, hence not standard. But can be used for restore on the same machine (For taking backup from commit_log_dir). If used on other machine(s) has to be in the same topology. Can it

Re: Optimal backup strategy

Same topology means the restore node should got the same tokes with the backup nodes ; ex : backup node1(1/2/3/4/5) node2(6/7/8/9/10) restore : nodea(1/2/3/4/5) nodeb(6/7/8/9/10) so node1's commitlog can be replay on nodea . Adarsh Kumar 于2019年11月29日周五 下午2:03写道： > Thanks Ahu and Hussein, >

Re: Optimal backup strategy

If you need backup for this environment, you should use snapshot and incremental backups. commit log backup solution depends on your environment and application. For example you can use RAID 1 on commit log disk to be safe against hardware failure. *VafaTech.com - A Total Solution for Data Gatheri

Re: Optimal backup strategy

1. It's recommended to use commit log after one node failure. Cassandra has many options such as replication factor as substitute solution. 2. Yes, right. *VafaTech.com - A Total Solution for Data Gathering & Analysis* On Fri, Nov 29, 2019 at 9:33 AM Adarsh Kumar wrote: > Thanks Ahu and Hussei

Re: Optimal backup strategy

Thanks Hossein, Just one more question is there any special SOP or consideration we have to take for multi-site backup. Please share any helpful link, blog or steps documented. Regards, Adarsh Kumar On Sun, Dec 1, 2019 at 10:40 PM Hossein Ghiyasi Mehr wrote: > 1. It's recommended to use commi

Re: Optimal backup strategy

I am sorry! This is true. I forgot "*not*"! 1. It's *not* recommended to use commit log after one node failure. Cassandra has many options such as replication factor as substitute solution. *VafaTech.com - A Total Solution for Data Gathering & Analysis* On Tue, Dec 3, 2019 at 10:42 AM Adarsh Kum

What is your backup strategy for Cassandra?

Hello everyone, I'm new to this mailing list, and still fairly new to Cassandra. I'm a systems administrator and have had a 3-node Cassandra cluster with a replication factor of 3 running in Production for about a year now. We have about 200 GB of data per node currently. Up until recently I ha

Re: What is your backup strategy for Cassandra?

On Sun, Sep 6, 2015 at 12:32 AM, Gene wrote: > I've seen quite a few blog posts here and there about various back up > strategies. I'm wondering if anyone on this list would be willing to share > theirs. > https://github.com/JeremyGrosser/tablesnap > Things I'm curious about: > > 1. Data size

Re: What is your backup strategy for Cassandra?

This seems like an apt time to quote [1]: > Remember that you get 1 point for making a backup and 10,000 points for restoring one. Restoring from backups is my goal. The commonly recommended tools (tablesnap, cassandra_snapshotter) all seem to leave the restore operation as a pretty complicated

Re: What is your backup strategy for Cassandra?

On Thu, Sep 17, 2015 at 7:46 PM, Marc Tamsky wrote: > This seems like an apt time to quote [1]: > > > Remember that you get 1 point for making a backup and 10,000 points for > restoring one. > > Restoring from backups is my goal. > > The commonly recommended tools (tablesnap, cassandra_snapshotte

Re: What is your backup strategy for Cassandra?

org>> Subject: Re: What is your backup strategy for Cassandra? On Thu, Sep 17, 2015 at 7:46 PM, Marc Tamsky mailto:mtam...@gmail.com>> wrote: This seems like an apt time to quote [1]: > Remember that you get 1 point for making a backup and 10,000 points for > restoring o

Re: What is your backup strategy for Cassandra?

de, and cp -r files over. John > > From: Maciek Sakrejda > Reply-To: Cassandra Maillist > Date: Friday, September 18, 2015 at 2:09 PM > To: Cassandra Maillist > Subject: Re: What is your backup strategy for Cassandra? > > On Thu, Sep 17, 2015 at 7:46 PM, Marc Tamsky wrote: >

Re: What is your backup strategy for Cassandra?

request a demo today! [cid:A671941A-2E52-4BB7-B7F8-994DC2C6BDB6] From: John Wong mailto:gokoproj...@gmail.com>> Reply-To: Cassandra Maillist mailto:user@cassandra.apache.org>> Date: Friday, September 18, 2015 at 8:02 PM To: Cassandra Maillist mailto:user@cassandra.apache.org>> Subje

Re: What is your backup strategy for Cassandra?

> > [image: Trilio-Business Assurance_300 Pixels] <http://www.triliodata.com/> > > *Experience Trilio* *in action*, please *click here > * to request a demo today! > > > From: John Wong > Reply-To: Cassandra Maillist > Date: Friday, September 18, 2015 at 8:02 PM