Is using the memory filesystem recommended? It seems that if all the configurations JR needs can be kept in memory, they must be creatable at runtime from the repo.xml.
The basic thing is this -- if all PMs are db backed, in the case of disk failure we should be able to get a repo back up and running, and be able to restore our repo content. (assuming the db is backed up). all of our base configs (repo.xml, and any namespace/nodetype files) will be kept and source control and are available to the application. It seems the stuff saved in the FM is arranged at runtime. On Tue, Aug 12, 2008 at 3:40 PM, Alexander Klimetschek <[EMAIL PROTECTED]>wrote: > On Tue, Aug 12, 2008 at 9:12 PM, Michael Harris > <[EMAIL PROTECTED]> wrote: > > So if I went with all oracle backed PMs and the default derby FS, would I > > have to back up the repo.home dir for disaster recovery? Or will the > > repository.xml be enough (so it can replace the workspace.xml files, and > > acknowledging that I would lose my lucene indexes)? > > Besides the data in the PMs (and the optional lucene indexes), you > will have to backup the namespaces and nodetypes files (under > <repo-home>/repository/namespaces and nodetpyes) - if your application > registers new namespaces and nodetypes -, the repository.xml, all > workspace.xml files and the optional datastore. If you use a > DbFileSystem, the namespaces and nodetypes should be contained within, > so backing up the db data in that case is sufficient. > > Regards, > Alex > > -- > Alexander Klimetschek > [EMAIL PROTECTED] > -- --------------------- Michael Harris
