Each mutation is applied to the commit log before being applied to the memtable. On server start the SSTables are read before replaying the commit logs. This is part of the crash only software design and happens for every start.
AFAIk there is no facility to snapshot commit log files as they are closed. The best advice would be to to keep them on a mirror set for durability. Cheers ----------------- Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 29/04/2012, at 1:04 AM, Roshan 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-queston-regarding-commitlogs-tp7508823.html > Sent from the cassandra-u...@incubator.apache.org mailing list archive at > Nabble.com.
