jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nilay Parmar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCR-3646) Search index backup and restore strategy
Date Wed, 14 Aug 2013 06:30:51 GMT

     [ https://issues.apache.org/jira/browse/JCR-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Nilay Parmar updated JCR-3646:

    Environment: win server, java1.7 64bit  (was: win server, java1.7 654bit)
> Search index backup and restore strategy
> ----------------------------------------
>                 Key: JCR-3646
>                 URL: https://issues.apache.org/jira/browse/JCR-3646
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: indexing
>    Affects Versions: 2.6
>         Environment: win server, java1.7 64bit
>            Reporter: Nilay Parmar
> We have a standalone jackrabbit configured with java1.7(64-bit) on windows OS.
> We have a 700GB of datastore at production and it increases with 2000 documents daily.
> Now, we are planning to have a recovery strategy from any unexpected index corruption(failure).
> For that we can take backup of the indexes on regular basis(weekly).
> When there is any problem and we restore the latest backup(may be 2 days old), does it
create indexes of those DELTA documents(added after latest backup)? Or re-index from scratch
is the only option?
> What should be the restore strategy?
> If this is not the correct way to recover from loss then please suggest any other solution.
> I did post this question in mailing list but yet to receive anything and as this blocks
the production, we need to find solution ASAP.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message