Concerning the backup strategy, I see two points : 1) Backup/recover config files
This can be achieved through web admin interface. A zip file will be generated containing the config files and named according to the current system date. In case of trouble (after parameter modification or reinstallation), the user can reinstall files 2) Log rotation (already discussed) : can be defined in the existing cfg file 3) Keep image of the bundles installed (useful to roll back install of project = sum of bundles) With this feature, the deployer can be roll back an installation in case of problem Charles On Thu, Apr 2, 2009 at 3:16 PM, Jamie G. <[email protected]> wrote: > I'd like to know more about the Backup strategy too. Are we looking > for some best practices documentation or something more comprehensive > (such as disaster recovery scenario)? > > We already have some fail over support via the kernel as Guillaume has > noted. > > Cheers, > Jamie > > >> - Backup strategy, > > > > Please explain ? Is this related to > > > http://servicemix.apache.org/kernel/67-configuring-failover-deployments-available-in-110.html > > ? >
