Yes, you shouldn’t delete the system directory. Next steps are …reconfigure the test cluster with new IP addresses, clear the gossiping information and then boot the test cluster.
If you are running Cassandra on VMware, then you may also want to look at this solution<http://www.triliodata.com/wp-content/uploads/2015/04/Cassandra-Trilio-Data-Sheet4.pdf> from Trilio Data, where you can create a Cassandra backup and restore it to a Test Cluster. Regards, Sanjay _________________ Sanjay Baronia VP of Product & Solutions Management TrilioData (c) 508-335-2306 sanjay.baro...@triliodata.com<mailto:sanjay.baro...@triliodata.com> [Trilio-Business Assurance_300 Pixels]<http://www.triliodata.com/> Experience Trilio in action, please click here<mailto:i...@triliodata.com?subject=Demo%20Request.> to request a demo today! From: Anton Koshevoy [mailto:nowa...@gmail.com] Sent: Monday, June 8, 2015 4:42 PM To: user@cassandra.apache.org Subject: Re: Restoring all cluster from snapshots Rob, thanks for the answer. I just follow instruction from http://docs.datastax.com/en/cassandra/2.1/cassandra/operations/ops_snapshot_restore_new_cluster.html If not to remove system table data, the test cluster starts interfering to a production cluster. How Can I avoid this situation? On June 8, 2015 at 9:48:30 PM, Robert Coli (rc...@eventbrite.com<mailto:rc...@eventbrite.com>) wrote: On Mon, Jun 8, 2015 at 6:22 AM, Anton Koshevoy <nowa...@gmail.com<mailto:nowa...@gmail.com>> wrote: - sudo rm -rf /db/cassandra/cr/data0*/system/* This removes the schema. You can't load SSTables for column families which don't exist. =Rob
