If you look at the latest version of Magnolia you would see that the repo
configuration files (WEB-INF/config/repo-conf/jackrabbit-*.xml) it comes with
have already datastore configured.
<DataStore class="org.apache.jackrabbit.core.data.FileDataStore">
<param name="path" value="${rep.home}/repository/datastore"/>
<param name="minRecordLength" value="1024"/>
</DataStore>
You should still be able to use magnolia-tools.
Backup is more of a problem as you need to do backup of DB and the FS at the
same time (ideally between transactions which can be ensured only when the
instance is down). You can also take advantage of some DBs being able to expose
themselves as virtual file system and have that FS used as target for the data
store (the advantage is still using simple API to store and access the files
and having better performance then when going over LOBs). Obviously if your
only aim is to reduce space used by DB, then you want to use different FS for
data store and have to deal with heterogeneity of the backup.
The problem is definitively migration. You can either use the migration path
recommended at JR website, or (which I would recommend), you can just export
everything from the repo in xml, install new repo with the required storage
configuration and import everything there.
The benefit of export/import is 3 fold:
-- you can do and re-do the procedure multiple times testing different
configurations with just one export and not to mess with your production data.
-- going via export/import will evict the versions and on a long running
installation with many updates to content over the years significantly reduce
the size of the DB.
-- you don't need to re-import the content that is no longer necessary, yet you
still have it in form of export in case you ever need it.
HTH,
Jan
On Nov 29, 2010, at 2:33 PM, Andrea Castelli wrote:
> Dear Magnolians,
> I'm investigating about the feasibility to add the FileDataStore to an
> existing Magnolia instance.
>
> http://wiki.apache.org/jackrabbit/DataStore
> http://wiki.magnolia-cms.com/display/WIKI/Changing+Jackrabbit+PersistenceManager
> http://wiki.apache.org/jackrabbit/BackupAndMigration
>
> The scenario is the following: month after month, site after site, file after
> file the DB grows up. (Magnolia 4.3.1+Jackrabbit 1.6.1+MySQL)
> The solution is: change to the FileDataStore.
>
> What does this solution imply? Are there scenarios where this solution can be
> dangerous? For example, I never can be
> able to rebuild indexes or magnolia-tools are not thinked to be used in such
> configuration? Anything else?
>
> How can I perform this solution? Do I need to migrate the whole workspace, or
> do I loss data? How do I schedule the Garbace Collector?
>
> If you already experimented this solution, what are the best practices?
>
> Thank you.
>
> Best regards.
> Andrea Castelli
-
Best regards,
Jan Haderka, PhD.
Magnolia International Ltd.
http://www.magnolia-cms.com
http://twitter.com/magnolia_cms
http://facebook.com/Magnolia
--------------------------------------
Magnolia® - Simple Open-Source Content Management
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
