MySQL Enterprise Backup (MEB): Backup Fails; Lost Connection to MySQL Server During Query; Error 2006: MySQL Server Has Gone Away; This Backup Operation Cannot be Logged

(Doc ID 1381365.1)

Last updated on SEPTEMBER 11, 2017

Applies to:

MySQL Enterprise Backup - Version 3.5 to 3.8 [Release 3.5 to 3.8]
Information in this document applies to any platform.

Symptoms

When attempting to backing up a large database, the following - or similar - errors occur.

WARNING! Backup Logging: Execution of prepared statement for inserting a row into backup progress table failed. with error Lost connection to MySQL server during query. This backup operation cannot be logged. mysqlbackup.exe: ERROR: Ping failed: MySQL server has gone away
mysqlbackup.exe: ERROR: Backup of non-innodb tables failed.!
mysqlbackup.exe: ERROR: mysql query: 'UNLOCK TABLES': MySQL server has gone away
mysqlbackup.exe: ERROR: Could not unlock the tables which were locked earlier.
mysqlbackup.exe: ERROR: mysql query: 'UNLOCK TABLES': MySQL server has gone away
mysqlbackup.exe: ERROR: Could not unlock the tables which were locked earlier.
Error: operation failed. global_error_count: 6 backup_config.error_count: 1
mysqlbackup.exe: WARNING: Backup Logging: The MySQL query 'SET SESSION SQL_MODE='' failed with Error 2006: MySQL server has gone away. This backup operation cannot be logged.


Another common symptom is that the mysql.backup_progress table is missing the row for locking the MyISAM tables even though the backup is past that point.

mysql> SELECT `current_time`, current_state, error_code, error_message FROM mysql.backup_progress WHERE backup_id = '13196613032909695';
+---------------------+----------------------+------------+---------------+
| current_time        | current_state        | error_code | error_message |
+---------------------+----------------------+------------+---------------+
| 2011-10-27 07:35:03 | Started mysqlbackup. | 0          | NO_ERROR      |
+---------------------+----------------------+------------+---------------+
1 row in set (0.00 sec)

Changes

The issue can be triggered by either of the following changes:

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms