I wrote a simple backup utility for a Collection that uses the replication handler, see: https://github.com/LucidWorks/solr-scale-tk/blob/master/src/main/java/com/lucidworks/SolrCloudTools.java#L614 feel free to borrow / steal if useful.
On Mon, Apr 6, 2015 at 12:42 PM, Davis, Daniel (NIH/NLM) [C] <daniel.da...@nih.gov> wrote: > I withdraw this question - it is covered in the Solr 5 reference manual. > The suggestion is to use the replication handler, which suggests that this > scheme still works. That's how I will go. > > From: Davis, Daniel (NIH/NLM) [C] > Sent: Monday, April 06, 2015 2:29 PM > To: solr-user@lucene.apache.org > Subject: Backup within SolrCloud > > So, we have replication, but what if something bad is indexed into the > cluster, or someone accidentally deletes *:* on some collection? > How do people manage backup in SolrCloud? > > I'm primarily interested in smaller indexes where backup is at all feasible. > I imagine a system such as Facebook really has to hope it stays up and maybe > do something similar to log shipping, e.g. keep intermediate results that > were fed into Solr. My applications are likely to be a bit smaller, and > classic system backups apply. > > Thanks, > > Dan Davis, Systems/Applications Architect (Contractor), > Office of Computer and Communications Systems, > National Library of Medicine, NIH >
