Need to dump both routines, and any event(s) that trigger those routi… #27
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Also... Is there a reason you used --skip-extended-insert on the data export? This option makes importing take FOREVER because it doesn't take advantage of bulk inserts. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It is not sufficient to export just the routines. You also need to export any events that are used to trigger those routines. This is especially key for those of us that have partitioned our history tables, as the routines are how we maintain the partitions.
This has been tested to work for both export and import on Zabbix 3.0.31 release. As this is a function of the mysqldump command, I would expect this to work just fine with any other Zabbix version.