Yes, I agree about making sure the backups actually work, whatever the approach. Thanks for your reply and all you've contributed to the Solr/Lucene community. The Lucene in Action book has been a huge help to me.
Paul On Wed, Jan 9, 2013 at 12:16 PM, Otis Gospodnetic < otis.gospodne...@gmail.com> wrote: > Hi Paul, > > Hot backup is OK. There was a thread on this topic yesterday and the day > before. But you should always try running from backup regardless of what > anyone says here, because if you have to do that one day.... you want to > know you verified it :) > > Otis > -- > Solr & ElasticSearch Support > http://sematext.com/ > > > > > > On Wed, Jan 9, 2013 at 3:12 PM, Paul Jungwirth > <p...@illuminatedcomputing.com>wrote: > > > > Are you sure a commit didn't happen between? > > > Also, a background merge might have happened. > > > > > > As to using a backup, you are right, just stop solr, > > > put the snapshot into index/data, and restart. > > > > > > This was mentioned before but seems not to have gotten any attention: > can't > > you use the ReplicationHandler by just going to a URL like this?: > > > > > > > > > http://host:8080/solr/replication?command=backup&location=/home/jboss/backup > > > > The 2nd edition Lucene in Action book describes a way to take hot backups > > without stopping your IndexWriter (pp. 374ff), and it appears that > > ReplicationHandler uses a similar strategy if I'm reading the code > > correctly (Solr 3.6.1; I guess v4 is the same). > > > > It'd be great if someone more knowledgeable could confirm that you can > use > > the ReplicationHandler to take hot backups. I'm surprised to see such a > > long thread about starting/stopping index jobs when there is such an easy > > answer. Or am I mistaken and at risk of corrupt backups if I use it? > > > > Thanks, > > Paul > > > > -- > > _________________________________ > > Pulchritudo splendor veritatis. > > > -- _________________________________ Pulchritudo splendor veritatis.
