Re: backup/restore from sstable files ?
On Sat, Nov 10, 2012 at 3:00 PM, Tyler Hobbs ty...@datastax.com wrote: For an alternative that doesn't require the same ring topology, you can use the bulkloader, which will take care of distributing the data to the correct nodes automatically. For more details on which cases are best for the different bulk loading techniques : http://palominodb.com/blog/2012/09/25/bulk-loading-options-cassandra =Rob -- =Robert Coli AIMGTALK - rc...@palominodb.com YAHOO - rcoli.palominob SKYPE - rcoli_palominodb
Re: backup/restore from sstable files ?
On Fri, Nov 9, 2012 at 6:04 PM, Rob Coli rc...@palominodb.com wrote: some of my colleagues seem to use this method to backup/restore a cluster, successfully: on each of the node, save entire /cassandra/data/ dir to S3, then on a new set of nodes, with exactly the same number of nodes, copy back each of the data/ dir. then boot up cluster. Yep, that works as long as the two clusters have the same tokens and replication strategies. For an alternative that doesn't require the same ring topology, you can use the bulkloader, which will take care of distributing the data to the correct nodes automatically. -- Tyler Hobbs DataStax http://datastax.com/
Re: backup/restore from sstable files ?
On Thu, Nov 8, 2012 at 5:15 PM, Yang tedd...@gmail.com wrote: some of my colleagues seem to use this method to backup/restore a cluster, successfully: on each of the node, save entire /cassandra/data/ dir to S3, then on a new set of nodes, with exactly the same number of nodes, copy back each of the data/ dir. then boot up cluster. Yep, that works as long as the two clusters have the same tokens and replication strategies. but I wonder how it worked: doesn't the system keyspace store information specific to the current cluster, such as my sibling nodes in the cluster, my IP ?? all these would change once you copy the frozen data files onto a new set of nodes. Yes, for this reason you should not restore the system keyspace files (except, optionally, Schema.). Definitely you should not restore LocationInfo. LocationInfo contains ip-to-token mappings. Also you should make your target cluster have a unique cluster name, and the old cluster name is also stored in LocationInfo... =Rob -- =Robert Coli AIMGTALK - rc...@palominodb.com YAHOO - rcoli.palominob SKYPE - rcoli_palominodb
