We have also made backup and restore for Apache Cassandra,backup process are 1.do incremental backup for flushed sstable ;do incremental backup for commitlog ; 2.do snapshot for the cluster periodically,also meta info are needed to backup(token and table info)； 3.for exception like node joining and move(if exist),leave ， refresh the meta info backup;
restore 1.use incremental sstable to reduce the number of commitlog for restore ,for log replay cost much time ; 2.all sstable can do bulkload(just node refresh （so ,my restore node's number need to be the same as backup,for sstableloader, it cost much time than this method,though use loader does not need the node to be same as backup）) Connor Lin <linba...@gmail.com> 于2019年8月8日周四 上午10:17写道： > Hi Krish, > > It is recommended to have backups. Although I haven't practiced it myself, > but I find this might be helpful. > > https://thelastpickle.com/blog/2018/04/03/cassandra-backup-and-restore-aws-ebs.html > > Sincerely yours, > > Connor Lin > > > On Thu, Aug 8, 2019 at 5:47 AM Krish Donald <gotomyp...@gmail.com> wrote: > >> Hi Folks, >> >> First question is , Do you take backup for your cassandra cluster ? >> If answer is yes then question follows: >> 1. How do you take backup ? >> 1.1 ) Is it only snapshot? >> 1.2 ) We are on AWS with very large cluster around 51 nodes >> with 1TB data on each node. >> 1.3) Do you take backup and move it to S3 ? >> >> 2. If you take backup, how restore process worked for you? >> >> Thanks >> Krish >> > -- you are the apple of my eye !
