The simplest way is to stop all index writing (close the IndexWriter), do the copy, then start your IndexWriter again.
If that's a problem (usually it is!) then use SnapshotDeletionPolicy to protect the commit point (ie prevent any of the files it uses from being deleted) while you are making the copy... this way you can take a hot backup without pausing index writing... Mike McCandless http://blog.mikemccandless.com On Fri, May 25, 2012 at 7:02 AM, Ganesh <emailg...@yahoo.co.in> wrote: > Hello all, > > We want to place our search db in SAN drive and want to replicate the data to > another SAN. We have a replication software to do this process. > > My question is whether we could do that for search db? While indexing (for > testing purpose), i just copied the db files and dropped in another system. > When i started my application in another system, I could see my search > database whiped out. Only write lock remains. The behaviour is unpredictable. > > I am not using SnapshotDeletionPolicy. Is that any other way to acheive this > using SAN replicator? > > Regards > Ganesh > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
