| Bug #74064 | Add support for backup_history | ||
|---|---|---|---|
| Submitted: | 25 Sep 2014 8:37 | Modified: | 25 Sep 2014 9:39 |
| Reporter: | Daniël van Eeden (OCA) | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Command-line Clients | Severity: | S3 (Non-critical) |
| Version: | 5.6 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[25 Sep 2014 9:39]
MySQL Verification Team
Hello Daniël, Thank you for the feature request! Indeed, good to have mysqldump logging such details so that it can be used by the MySQL Enterprise Monitor product and/or other tools to easily monitor backup operations. Workaround - Imho, one can manually track these details externally(customized shell script +mysqldump to store in relational format or log into text files) which may or may not be compatible for monitoring tools. Thanks, Umesh
Description: MySQL Enterprise Backup uses mysql.backup_{history,progress}. It would be helpfull if mysqldump would also support this. How to repeat: Backup a database with mysqldump and query on the backup_history table. Suggested fix: Add support for backup_history