You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by "Cech. Ulrich" <Ul...@aeb.de> on 2010/05/19 17:22:21 UTC

Jackrabbit and WORM

Hi altogether,

I wanted to know how jackrabbit can be used in judicial environment in conjunction with a WORM storage system.
Background: The storage system must store the data, so that the data cannot be edited, deleted, overwritten, so the best way to go is to use a WORM. There is a good system (FAST LTA) which does the work (the datastore directory is then on a network share, the the Silent Cube stores the data files undeletable).

But another law says, that you need to delete the data, if a customer cancel a contract with you, and you have to delete his data from your storage (that is impossible for a WORM).
So, is there any experience dealing with this? Can jackrabbit be configured to store the data encrypted in his datastore? If the customer cancells the contract, you can delete the key and the data is lost (equal to deleted).

Any hints or links are very welcome.

Thanks all in advance,
Ulrich


Re: Jackrabbit and WORM

Posted by Thomas Müller <th...@day.com>.
Hi,

> written to read-only media

Do you mean written to write-only media? The DataStore implementation
does not support this feature currently, however you could probably
change the FileDataStore to support it. Instead of writing the
temporary file to the datastore directory, it would have to be written
to a different place (the temp directory for example). If you don't
have a temp directory then it's a bit more complicated (binaries would
need to be split into smaller blocks that fit in memory).

Regards,
Thomas


On Wed, Jul 14, 2010 at 11:42 AM, Cech. Ulrich <Ul...@aeb.de> wrote:
> I have problems using JackRabbit with a storage-system, where files could only be added, but not changed or deleted.
> I found out, that in BinaryImpl.class there is created a TransientFileFactory, where the stream is written in a temporary file and later be deleted. If this deletion fails, I get an exception
> ...
> Caused by: java.io.IOException: Can not rename c:\temp\cr20fs\repository\datastore\tmp21866.tmp to c:\temp\cr20fs\repository\datastore\8d\54\82\8d548201d39d7594d182c2a3901fa38dfeebc6b3 (media read only?)
> ...
>
> I tried to set the DataStore parameter "minRecordLength" to a very high value, so that the stream is handled in memory, but this is limited to the available heap space and so not applicable.
>
> Has anyone some experiences with Jackrabbit and read-only media? Can it be configured, that only the repository and the versions are written to read-only media, but other files (like the Lucene index, which could be well configured to some other directory, so that's no problem) is written to some "normal" storage system?
>
> Many thanks in advance,
> Ulrich
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Fabián Mandelbaum [mailto:fmandelbaum@gmail.com]
> Gesendet: Donnerstag, 20. Mai 2010 23:10
> An: users@jackrabbit.apache.org
> Betreff: Re: Jackrabbit and WORM
>
> Hello Urlich, Tom,
>
> I think this is easy to test: just chmod -w all files (that is, make
> them read-only) on a running *test* repository, and try to perform an
> operation that will make modifications to the repo.
>
> On Thu, May 20, 2010 at 3:10 AM, Cech. Ulrich <Ul...@aeb.de> wrote:
>> Hi Tom,
>>
>> thanks for your response.
>>
>> Yes, I think, "every customer has it's own repository" is the way to go. But at a high number of customers, the solution with "every customer on a separate disk" is not quite possible.
>>
>> But I have an additional question: How does Jackrabbit react, of I want to remove a node, but the file in the file-system cannot be deleted (WORM-like)?
>>
>> Thanks again,
>> Ulrich
>>
>>
>>
>
>
>
> --
> Fabián Mandelbaum
> IS Engineer
>

AW: Jackrabbit and WORM

Posted by "Cech. Ulrich" <Ul...@aeb.de>.
I have problems using JackRabbit with a storage-system, where files could only be added, but not changed or deleted.
I found out, that in BinaryImpl.class there is created a TransientFileFactory, where the stream is written in a temporary file and later be deleted. If this deletion fails, I get an exception
...
Caused by: java.io.IOException: Can not rename c:\temp\cr20fs\repository\datastore\tmp21866.tmp to c:\temp\cr20fs\repository\datastore\8d\54\82\8d548201d39d7594d182c2a3901fa38dfeebc6b3 (media read only?)
...

I tried to set the DataStore parameter "minRecordLength" to a very high value, so that the stream is handled in memory, but this is limited to the available heap space and so not applicable.

Has anyone some experiences with Jackrabbit and read-only media? Can it be configured, that only the repository and the versions are written to read-only media, but other files (like the Lucene index, which could be well configured to some other directory, so that's no problem) is written to some "normal" storage system?

Many thanks in advance,
Ulrich



-----Ursprüngliche Nachricht-----
Von: Fabián Mandelbaum [mailto:fmandelbaum@gmail.com] 
Gesendet: Donnerstag, 20. Mai 2010 23:10
An: users@jackrabbit.apache.org
Betreff: Re: Jackrabbit and WORM

Hello Urlich, Tom,

I think this is easy to test: just chmod -w all files (that is, make
them read-only) on a running *test* repository, and try to perform an
operation that will make modifications to the repo.

On Thu, May 20, 2010 at 3:10 AM, Cech. Ulrich <Ul...@aeb.de> wrote:
> Hi Tom,
>
> thanks for your response.
>
> Yes, I think, "every customer has it's own repository" is the way to go. But at a high number of customers, the solution with "every customer on a separate disk" is not quite possible.
>
> But I have an additional question: How does Jackrabbit react, of I want to remove a node, but the file in the file-system cannot be deleted (WORM-like)?
>
> Thanks again,
> Ulrich
>
>
>



-- 
Fabián Mandelbaum
IS Engineer

Re: Jackrabbit and WORM

Posted by Fabián Mandelbaum <fm...@gmail.com>.
Hello Urlich, Tom,

I think this is easy to test: just chmod -w all files (that is, make
them read-only) on a running *test* repository, and try to perform an
operation that will make modifications to the repo.

On Thu, May 20, 2010 at 3:10 AM, Cech. Ulrich <Ul...@aeb.de> wrote:
> Hi Tom,
>
> thanks for your response.
>
> Yes, I think, "every customer has it's own repository" is the way to go. But at a high number of customers, the solution with "every customer on a separate disk" is not quite possible.
>
> But I have an additional question: How does Jackrabbit react, of I want to remove a node, but the file in the file-system cannot be deleted (WORM-like)?
>
> Thanks again,
> Ulrich
>
>
>



-- 
Fabián Mandelbaum
IS Engineer

AW: Jackrabbit and WORM

Posted by "Cech. Ulrich" <Ul...@aeb.de>.
Hi Tom,

thanks for your response.

Yes, I think, "every customer has it's own repository" is the way to go. But at a high number of customers, the solution with "every customer on a separate disk" is not quite possible.

But I have an additional question: How does Jackrabbit react, of I want to remove a node, but the file in the file-system cannot be deleted (WORM-like)?

Thanks again,
Ulrich



Re: Jackrabbit and WORM

Posted by Tom Anderson <to...@e2x.co.uk>.
On Wed, 19 May 2010, Cech. Ulrich wrote:

> I wanted to know how jackrabbit can be used in judicial environment in 
> conjunction with a WORM storage system. Background: The storage system 
> must store the data, so that the data cannot be edited, deleted, 
> overwritten, so the best way to go is to use a WORM. There is a good 
> system (FAST LTA) which does the work (the datastore directory is then 
> on a network share, the the Silent Cube stores the data files 
> undeletable).
>
> But another law says, that you need to delete the data, if a customer 
> cancel a contract with you, and you have to delete his data from your 
> storage (that is impossible for a WORM). So, is there any experience 
> dealing with this? Can jackrabbit be configured to store the data 
> encrypted in his datastore? If the customer cancells the contract, you 
> can delete the key and the data is lost (equal to deleted).

Keep each customer's data in a separate repository, on a separate disk. If 
they cancel their contract, remove the disk and send it to them, with 
instructions on how to destroy it securely. Charge them for this.

tom

-- 
Tom Anderson                |            e2x Ltd, 8 Elder Street, London E1 6BT
(e) tom.anderson@e2x.co.uk  |  (m) +44 (7960) 989794  |  (f) +44 (20) 7194 8016