A postCommit hook (configured in solrconfig.xml) is called in a safe
place for every commit.
You could have a program as a hook that normally did nothing unless
you had previously signaled to make a copy of the index.
Then I will give the postCommit trigger a try and hope that while the
trig
On Jan 4, 2008 8:44 AM, Jörg Kiegeland <[EMAIL PROTECTED]> wrote:
> > If you want to copy the hard files from the data/index directory, yes,
> > you'll probably want to shut down the server first. You may be able to get
> > away with leaving the server up but stopping any index/commit operations,
If you want to copy the hard files from the data/index directory, yes, you'll
probably want to shut down the server first. You may be able to get away with
leaving the server up but stopping any index/commit operations, but I could be
wrong.
How do I stop remote clients to do index/commit
ry 03, 2008 11:00 AM
To: solr-user@lucene.apache.org
Subject: Re: Backup of a Solr index
Charlie Jackson wrote:
> Solr indexes are file-based, so there's no need to "dump" the index to a
> file.
>
But however one has first to shutdown the Solr server before copying the
i
Charlie Jackson wrote:
Solr indexes are file-based, so there's no need to "dump" the index to a file.
But however one has first to shutdown the Solr server before copying the
index folder?
In terms of how to create backups and move those backups to other servers, check out this page http://
If you're writing to disk, you can minimize the chance of an
inconsistent index by hardlinking the files first (cp -l)
-Mike
On 2-Jan-08, at 8:10 AM, Charlie Jackson wrote:
Solr indexes are file-based, so there's no need to "dump" the index
to a file.
In terms of how to create backups and
Solr indexes are file-based, so there's no need to "dump" the index to a file.
In terms of how to create backups and move those backups to other servers,
check out this page http://wiki.apache.org/solr/CollectionDistribution.
Hope that helps.
-Original Message-
From: Jörg Kiegeland
