Why do you think that during a backup any write activity would corrupt your backup? Solr "backs up" live indexes all the time, that's what's happening, in effect, when you replicate from a master to a slave. There's no requirement that the master stop indexing. The replication "backup" command Ahmet told you about is using the same mechanism.
Solr/Lucene index segments are write-once. backup/replication essentially copies closed segments around which, since they aren't changing, aren't affected by other indexing activity. So the process is this: 1> a backup/replication starts. At this point, a list is made of all the currently-closed segments and these segments will NOT be deleted until the backup/replication is complete. 2> all the segments in <1> are copied. This is a complete snapshot of your index. 3> after all the segments are copied, they are released and may then be deleted in the normal merge process. Of course another way to do backups would be set up a machine that just does a replication (think of it as a "special slave") periodically. Another would be to have the master keep backups automatically, seesee: http://wiki.apache.org/solr/SolrReplication, and look for numberOfBackups. Best Erick On Fri, Mar 15, 2013 at 1:03 AM, vicky desai <vicky.de...@germinait.com>wrote: > Hi, > > I have a multi core setup and there is continuous updation going on in each > core. Hence I dont prefer a bckup as it would either cause a downtime or if > during a backup there is a write activity my backup will be corrupted. Can > you please suggest if there is a cleaner way to handle this > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-Replication-tp4047266p4047591.html > Sent from the Solr - User mailing list archive at Nabble.com. >
