Bug #55959 Capability to merge one MEM repository into another MEM repository

• Submitted: 13 Aug 2010 3:05
• Modified: 26 Aug 2010 12:28
• Reporter: Jonathon Coombes
• Status: Won't fix
• Category: MySQL Enterprise Monitor: Server
• Severity: S4 (Feature request)
• Version: 2.2.0
• OS: Any
• Assigned to: MEM Service Manager Devs
• CPU Architecture: Any
• Tags: mem, Merlin, repository

[13 Aug 2010 3:05] Jonathon Coombes

Description:
Request a tool or capability to allow one MEM repository to be merged into another one. This could be due to shifting data centers, or merging an older version into an existing new version (not upgrading).

How to repeat:
N/A

Suggested fix:
N/A

[26 Aug 2010 12:28] Enterprise Tools JIRA Robot

Mark Leith writes: 
This is actually more complicated than it seems, given the schema and the ETL process that would be required. Our only recommended migration path is to move the current installation to the new machine, and upgrade it in place there (or upgrade, then move, then start from there). 

We are setting this to "Won't fix" for now, given the engineering resources required for it. If more people request this we may re-evaluate this.