Bug #41222 Make it possible to save and restored the merlin configuration stored in the db
Submitted: 4 Dec 2008 11:28 Modified: 9 Jan 2015 10:06
Reporter: Simon Mudd (OCA) Email Updates:
Status: Closed Impact on me:
Category:MySQL Enterprise Monitor: Installing Severity:S4 (Feature request)
Version: OS:Any
Assigned to: Mark Leith CPU Architecture:Any

[4 Dec 2008 11:28] Simon Mudd
If anything goes wrong with the merlin installation it may be necessary to reinstall it. However when the whole configuration is stored in the db and thus gets lost. At least with a minor release it would be most helpful if we could save the "configuration" and then restore it into a freshly intalled merlin instance thus returning the configuration to it's previous state

How to repeat:
Install merlin
use it for a while.
Fill up the filesystem or break it a bit.
Have to reinstall a new version
The following configuration information is lost:
- user information
- servers and grouping and names
- rule configurations
- etc..

Suggested fix:
provide a script which can dump the minimum required db information to disk.
provide a similar script which can be run on a fresh installation (of the same major version) so that the previous configuration is maintained.
[13 Aug 2009 8:56] Eric Herman
in 2.1 the "dc_" tables are not needed for config information, so we should be able to dump the small tables and restore them and have all of the needed config info
[2 Mar 2010 13:49] MySQL Verification Team
An addition to the manual Appendix E.8 about backing up only the configuration without the historical data would be nice while waiting for the feature request. See Eric's message above.