The incremental backups are generated when the flush is complete (Only during the flush), If the node crash before the flush completes then the commit logs in the local node's backup for the data in memory. It wouldn't help to copy the Commit log across because they are not immutable (They are recycled).
There is commit log backup in 1.1.1 (Yet to be released) https://issues.apache.org/jira/browse/CASSANDRA-3690 Thanks, </VJ> On Sun, Apr 29, 2012 at 3:29 PM, Roshan <codeva...@gmail.com> wrote: > Hi > > Currently I am taking daily snapshot on my keyspace in production and > already enable the incremental backups as well. > > According to the documentation, the incremental backup option will create > an > hard-link to the backup folder when new sstable is flushed. Snapshot will > copy all the data/index/etc. files to a new folder. > > Question: > What will happen (with enabling the incremental backup) when crash (due to > any reason) the Cassandra before flushing the data as a SSTable (inserted > data still in commitlog). In this case how can I backup/restore data? > > Do I need to backup the commitlogs as well and and replay during the server > start to restore the data in commitlog files? > > Thanks. > > -- > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Cassandra-backup-question-regarding-commitlogs-tp7511918.html > Sent from the cassandra-u...@incubator.apache.org mailing list archive at > Nabble.com. >
