Hey Lee, the files that you still find in the file system are either configuration files for the repository (or workspaces) and the search indexes for each of the workspaces (JR uses Lucene for searching). Optionally there could be also big binary files in case you configured the datastore.
If you don't want to have anything at all in the filesystem, you can also configure DBFileSystem for jackrabbit (see JR documentation for details) and get everything to the DB. Also, the configuration files normally do not change unless you install new datatypes or change DB configuration so you don't need to backup them so often. Initial copy should be enough. Indexes will be recreated automatically if not found. The only drawback is that reindexing huge sites might take few minutes. Last but not least, in my experience MySQL is usually faster then Derby, so if it is slower for you, you might want to double check DB configuration. HTH, Jan On Mar 19, 2011, at 12:00 AM, Lee Haslup wrote: > Following the instructions on the Wiki (here) I was able to modify the > mangolia-enterprise-bundle-4.4.2-tomcat-bundle bundle to use a MS > SQL-Server-based persistence manager. But having done so I am not exactly > sure what, if anything, I have really accomplished. Maybe I have missed > something. > > My modified Magnolia instance runs fine. It has created 72 tables in my > SQL-Server database which appear to have data in them. So far, so good. > > But it has also written something like 600 files to the > magnoliaAuthor/repositories/... directories. These files have names like > magnoliaAuthor/repositories/magnolia/repository/namespaces/ns_reg.properties > and repositories/magnolia/workspaces/data\index/_0/_0.cfs. Magnolia appears > to need these files to open the repository. There is a boolean value in the > persistenceManager configuration that tells Jackrabbit to store blobs in the > file system (not in the database) and I was careful to set that to "false". > > As it is currently working in my installation, Jackrabbit stores a small > amount of information in the database and a rather-larger amount on the file > system -- and the two appear to need to be kept in sync for backups. Since > the SQL-Server persistence manager also seems to be slower than Derby, what > good is it, really? Or did I miss a step? > > Thanks, > > BigLeeH > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
