Hi Thomas, Thanks for you answer. This is also exactly what we already do in most cases ;-)
I guess currently it's a trade off: If you don't want to stop jackrabbit for making a backup, you must have a clustered node that you can dedicate to making the backup. Regards, Bart On Mon, Jun 15, 2009 at 11:49 AM, Thomas Müller <[email protected]> wrote: > Hi, > > If you use database persistence managers and a database journal, you > could use the following procedure: > > 1) stop the cluster node > 2) backup the lucene index, config files, and revision.log of this cluster > node > 3) later on, backup the persistence manager data, journal data, and data store > > This backup should be consistent because the journal includes the list > of changes, so the lucene index is updated. > > Regards, > Thomas > > On Tue, Jun 9, 2009 at 3:48 PM, KÖLL Claus<[email protected]> wrote: >> hi (thomas), >> >> your post was clear thanks for the info ... >> ok the lucene index is consistent but you will not get a snapshot from the >> repository >> as bart wrote. >> >> I see some problems with barts solution .. >> if you have a large repository a write lock that runs hours is not good >> but maybe some others have good ideas ... >> >> i have tested the environment as you mentioned with the cluster and it works >> fine at the >> moment for us because we can re-index the backup cluster in the background >> if we get >> a crash ... hopefully not :-) >> >> greets >> claus >> > -- Hippo B.V. - Amsterdam Oosteinde 11, 1017 WT, Amsterdam, +31(0)20-5224466 Hippo USA Inc. - San Francisco 101 H Street, Suite Q, Petaluma CA, 94952-3329, +1 (707) 773-4646 ----------------------------------------------------------------- http://www.onehippo.com - [email protected] -----------------------------------------------------------------
