RepositoryCopier and power breakdown

[Sa...@innovations.de]

Hi all,

 

we use the RepositoryCopier to backup our repository. That works good
for us until we had a power breakdown during the backup process. The
RepositoryCopier was copying the repository when the power cuts off. The
next start of Jackrabbit was unsuccessful. We could not start Jackrabbit
anymore until we deleted the lucene indexes from disc. After that it
seems that jackrabbit works correctly.

 

My question is: Is there a potential risk of data corruption (or data
loss) in jackrabbit when a power breakdown occurs? Is that issue related
to the RepositoryCopier or could we get the same error without it?

 

However, I do not have a stack trace anymore and it seems that it
happens not all the time if we try to fake a power breakdown. 

 

Any ideas what causes the problem? 

 

We are using Jackrabbit 1.6.0

 

Kind Regards

Sascha Theves

 

Re: RepositoryCopier and power breakdown

[Alan Chaney <al...@writingshow.com>]

Sascha.Theves@innovations.de wrote:
> Hi all,
>
>  
>
> we use the RepositoryCopier to backup our repository. That works good
> for us until we had a power breakdown during the backup process. The
> RepositoryCopier was copying the repository when the power cuts off. The
> next start of Jackrabbit was unsuccessful. We could not start Jackrabbit
> anymore until we deleted the lucene indexes from disc. After that it
> seems that jackrabbit works correctly.
>
>  
>
> My question is: Is there a potential risk of data corruption (or data
> loss) in jackrabbit when a power breakdown occurs? Is that issue related
> to the RepositoryCopier or could we get the same error without it?
>
>  
>   
You don't say what O/S you are using, but I think the best advice here 
is invest in an UPS (Uninterruptible Power Supply)
The most probable cause of your original problem was that filing system 
updates had not been flushed to disk. That has nothing to do with 
Lucene, Jackrabbit,
Java or even the operating system.

Providing power backup is the only sensible practice when dealing with 
sensitive data.

Regards

Alan Chaney



> However, I do not have a stack trace anymore and it seems that it
> happens not all the time if we try to fake a power breakdown. 
>
>  
>
> Any ideas what causes the problem? 
>
>  
>
> We are using Jackrabbit 1.6.0
>
>  
>
> Kind Regards
>
> Sascha Theves
>
>  
>
>
>
> !DSPAM:4b7434a5260441336712104!
>
>   

Re: RepositoryCopier and power breakdown

[Guo Du <mr...@gmail.com>]

On Thu, Feb 11, 2010 at 4:40 PM,  <Sa...@innovations.de> wrote:
> My question is: Is there a potential risk of data corruption (or data
> loss) in jackrabbit when a power breakdown occurs? Is that issue related
> to the RepositoryCopier or could we get the same error without it?
RepositoryCopier doesn't commit any change to the repository for
backup, so there is no chance that the backup could damage your
repository.

It may caused by some other factor such as db/filesystem crash on
event of power failure.

-Guo

Re: RepositoryCopier and power breakdown

[Marcel Reutegger <ma...@gmx.net>]

Hi,

On Thu, Feb 11, 2010 at 17:40,  <Sa...@innovations.de> wrote:
> Hi all,
>
>
>
> we use the RepositoryCopier to backup our repository. That works good
> for us until we had a power breakdown during the backup process. The
> RepositoryCopier was copying the repository when the power cuts off. The
> next start of Jackrabbit was unsuccessful. We could not start Jackrabbit
> anymore until we deleted the lucene indexes from disc. After that it
> seems that jackrabbit works correctly.
>
>
>
> My question is: Is there a potential risk of data corruption (or data
> loss) in jackrabbit when a power breakdown occurs? Is that issue related
> to the RepositoryCopier or could we get the same error without it?

I don't think this is related to the copier as other people already suggested.

please provide log files with the details of the failure if this
should happen again. thanks

regards
 marcel

>
>
> However, I do not have a stack trace anymore and it seems that it
> happens not all the time if we try to fake a power breakdown.
>
>
>
> Any ideas what causes the problem?
>
>
>
> We are using Jackrabbit 1.6.0
>
>
>
> Kind Regards
>
> Sascha Theves
>
>
>
>