Hi Indranil, I think it really depends on what makes a backup "correct" for you. Do you have some test you can run on that data? When I want to test my data I usually restore it in a new cluster (ie. on AWS) and use Spark to perform some cross-tests. This is a bit cumbersome nevertheless does the trick.
Best, On Tue, Aug 9, 2016 at 8:50 AM, INDRANIL BASU <indranil...@yahoo.com> wrote: > Thanks Rajath. We have atleast 20 millions of records, so count(*) with > limit and token is getting cumbersome. > Yes using nodetool snapshot. I know there is a nodetool verify, but i m > using C * 2.1 > Copy commands sometimes fails as well. > > So any better easy mechanism? > > *Thanks and regards,* > *-- Indranil Basu* > > > ------------------------------ > *From:* Rajath Subramanyam <rajat...@gmail.com> > *To:* user@cassandra.apache.org; INDRANIL BASU <indranil...@yahoo.com> > *Sent:* Monday, 8 August 2016 11:41 PM > *Subject:* Re: Verify cassandra backup and restore in C * 2.1 > > Hi Indranil, > > One approach is to do a row count on the original source table and the > table that is restored from backup. How are you backing up data ? I am > assuming you are issuing snapshot commands (either incremental or > otherwise). > > I hope this helps. > > - Rajath > > ------------------------ > Rajath Subramanyam > > > On Mon, Aug 8, 2016 at 4:29 AM, INDRANIL BASU <indranil...@yahoo.com> > wrote: > > Hello, > > How can we verify that cassandra data is backed up and restored > correctly? > > *-- IB* > > > > > > >
