jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacco van Weert <1111softw...@gmail.com>
Subject Re: alternative export - import strategy
Date Wed, 04 Feb 2009 09:28:36 GMT

We use the JeCARS backup tool for export and import. Within JeCARS itself,
it can make a "hot" backup by simply performing a GET operation on the

Without the binary data it is also possible to do a remote backup and
restore. With JeCARS there is also a JeCARS client helper library.
It has exportNode( deep ) and importNode( stream ) methods which delivers
the backup as stream.

For backup without JeCARS the backup tool cannot also export and import
existing Jackrabbit repository versions (also v1.5). It will create a big
file (non-XML) for node/properties and every binary content is stored in a
seperate file.
The resulting directory can be used for import. The import will always try
to complete even when properties are removed. (simple versioning nodes are
also supported).

   JeCARS -- http://jecars.sourceforge.net

On Tue, Feb 3, 2009 at 7:58 PM, Shailesh Mangal <
shailesh.mangal@getzephyr.com> wrote:

> While database export and import is not working for us when we move from
> windows to linux, I would like to explore alternative export - import
> strategies e.g. http://sourceforge.net/projects/jcr-backup
> We have lots of binary data, files etc. I would like to know if someone has
> successfully implemented backup and restore strategy and the tools used to
> accomplish the same.
Jacco van Weert -- 1111software@gmail.com
JCR Controller -- http://www.xs4all.nl/~weertj/jcr
JeCARS -- http://jecars.sourceforge.net

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message