I also think that's a good question and currently without a "use this" answer :-) I think it shouldn't be hard to write a Solr service querying ZK and replicate both conf and indexes (via SnapPuller or ZK itself) so that such a node is responsible to back up the whole cluster in a secure storage (NAS, EBS, etc.).
just my 2 cents, Tommaso 2012/9/21 Otis Gospodnetic <otis.gospodne...@gmail.com> > Sounds good. > > But I think this was still a good question: Is there a way to back up > an index that lives in SolrCloud and if so, how? > > Otis > Search Analytics - http://sematext.com/search-analytics/index.html > Performance Monitoring - http://sematext.com/spm/index.html > > > On Thu, Sep 20, 2012 at 7:35 PM, Upayavira <u...@odoko.co.uk> wrote: > > What sorts of failures are you thinking of? Power loss? Index > > corruption? Server overload? > > > > Could you keep somewhat remote replicas of each shard, but not behind > > your load balancer? > > > > Then, should all your customer facing nodes go down, those replicas > > would be elected leaders. When you bring the customer facing ones back, > > they would justd pull their indexes from your remote replicas, and you'd > > be good to go once more. > > > > Upayavira > > > > On Thu, Sep 20, 2012, at 10:30 PM, jimtronic wrote: > >> I'm thinking about catastrophic failure and recovery. If, for some > >> reason, > >> the cluster should go down or become unusable and I simply want to bring > >> it > >> back up as quickly as possible, what's the best way to accomplish that? > >> > >> Maybe I'm thinking about this incorrectly? Is this not a concern? > >> > >> > >> > >> > >> > >> -- > >> View this message in context: > >> > http://lucene.472066.n3.nabble.com/Backup-strategy-for-SolrCloud-tp4009291p4009297.html > >> Sent from the Solr - User mailing list archive at Nabble.com. >
