Not to my knowledge. You could do a delete all and then merge the index in with the core admin API, but that would be a less efficient copy basically, rather than a straight file move. There is not currently a restore command though. Also, keep in mind that unless you back up to a network store or I suppose another disk drive or something, your backup is pretty precarious.
- Mark On Jan 7, 2013, at 2:21 PM, Michel Dion <diom...@gmail.com> wrote: > Is it possible to restore an index (previously backed up) using the same > kind of http reste like request ? Something like > ...solr/replication?command=restore ? > > On Mon, Jan 7, 2013 at 2:12 PM, Mark Miller <markrmil...@gmail.com> wrote: > >> You should be able to continue indexing fine - it will just keep a point >> in time snapshot around until the copy is done. So you can trigger a backup >> at anytime to create a backup for that specific time, and keep indexing >> away, and the next night do the same thing. You will always have backed up >> to the point in time the backup command is received. >> >> - Mark >> >> On Jan 7, 2013, at 1:45 PM, Otis Gospodnetic <otis.gospodne...@gmail.com> >> wrote: >> >>> Hi, >>> >>> There may be a better way, but stopping indexing and then >>> using http://master_host:port/solr/replication?command=backup on each >> node >>> may do the backup trick. I'd love to see how/if others do it. >>> >>> Otis >>> -- >>> Solr & ElasticSearch Support >>> http://sematext.com/ >>> >>> >>> >>> >>> >>> On Mon, Jan 7, 2013 at 10:33 AM, LEFEBVRE Guillaume < >>> guillaume.lefeb...@cegedim.fr> wrote: >>> >>>> Hello, >>>> >>>> Using a SOLR Cloud architecture, what is the best procedure to backup >> and >>>> restore SOLR index and configuration ? >>>> >>>> Thanks, >>>> Guillaume >>>> >>>> >> >>
