Hi Andrea,
if the backup of server 1 includes the index files, then after a restore of the
files and a restart of the server jackrabbit will not re-index content because
the index is already present. instead jackrabbit on server 1 will trigger events
for the revisions that it missed while it was shutdown. this will also update
the index to the latest revision available on the database.
regards
marcel
Andrea K. wrote:
Hi all,
Can you help me to find the right solution to backup a clustered JR?
Details are:
1. JR on Oracle 10g database (repository and cluster tables) - NO BACKUP
PROBLEMS
2. Local directories (each server) with configuration files and indexes (+
revision.log)
How can I backup it to take the situation coherent to db and cluster nodes
view?
A question is (I describe a situation):
- Server 1 is updated to revision 120 (i.e.) and I backup it (server is
stopped).
- Server 2 is updated in the meanwhile to 124 (i.e.) and I backup it (server
is stopped).
- Server 1 is restarted and write some revisions up to 127.
- Server 1 is restarted and write some revisions up to 135.
If Server 1 crash and i re-apply backup indexes up to 120, will it work or
some revisions are skipped during Server1 initial reindex as generator is
itself?
Thanks a lot for your help.
BR,
Andrea -
