Chapter 11 Troubleshooting for MySQL Enterprise Backup

Table of Contents

11.1 Error codes of MySQL Enterprise Backup

11.2 Working Around Corruption Problems

11.3 Using the MySQL Enterprise Backup Logs

11.4 Using the MySQL Enterprise Backup Manifest

To troubleshoot issues regarding backup and restore with the MySQL Enterprise Backup product, consider the following aspects:

• Before troubleshooting any problem, familiarize yourself with the known limits and restrictions on the product, in Appendix A, MySQL Enterprise Backup Limitations.

• If the mysqlbackup command encounters problems during operating system calls, it returns the corresponding OS error codes. You might need to consult your operating system documentation for the meaning and solution of these error codes.

• The output from the mysqlbackup command is sent to stderr rather than stdout. By default, the same output is also saved to a log file in the backup_dir for use in error diagnosis. See Section 5.1.12, “Message Logging Options” for details on how to configure this logging feature.

• Incremental backups require care to specify a sequence of time periods You must record the final LSN value at the end of each backup, and specify that value in the next incremental backup. You must also make sure that the full backup you restore is prepared correctly first, so that it contains all the changes from the sequence of incremental backups.

• As the mysqlbackup command proceeds, it writes progress information into the mysql.backup_progress table. When the command finishes the backup operation, it records status information in the mysql.backup_history table. You can query these tables to monitor ongoing jobs, see how much time was needed for various stages, and check if any errors occurred.