MySQL Bugs: #52403: migrate server history from old instance to new

Bug #52403	migrate server history from old instance to new
Submitted:	26 Mar 2010 19:48
Reporter:	Kyle Joiner	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Enterprise Monitor	Severity:	S4 (Feature request)
Version:	2.1.0	OS:	Any
Assigned to:	Mark Matthews	CPU Architecture:	Any
Tags:	hostid, migration, server

Description:
In some upgrade situations the host id may need to be changed to correct duplicate ssh key problems.  When the host id is changed then history is not migrated to the new instance in the MySQL Enterprise Dashboard.

How to repeat:
Change the hostid in a MySQL enterprise agent installation and restart agent.  A new server will be created in the Enterprise Dashboard.  

Suggested fix:
Provide a mechanism to migrate the historical data to the new server instance.

Bug#56813 was marked as a duplicate of this one.

I think this should be classified as an S3 bug, as it is missing functionality and 'inconvenient usage for which a workaround exists'.

Please take into account, re-synchronizing of slaves and re-installation of a database as mentioned in the duplicate bug #56813.

Bug #56813 is not a duplicate of this. Bug #56813 describes the change of uuid WITHOUT any change within the configuration, hostid or SSH Key.

This Bug is about loosing history data when getting a new hostid.