MySQL Enterprise Backup (MEB) Reports An Invalid Binary Log Position; In Some Cases As 18446744073709551615 Or -1 (Doc ID 2043644.1)

Last updated on JULY 06, 2017

Applies to:

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

Symptoms

When creating a backup with MySQL Enterprise Backup 3.12.3 or earlier or 4.0 where the backup was created in one of the following ways:

then the binary log position is reported as invalid binary log position such as 18446744073709551615 or -1, but also in some cases what looks like a valid position.

The exact output depends on the MySQL Enterprise Backup version; in some cases even no output of the binary log file and position will be present (which is the correct output as the binary log file and position is unknown - see also the Cause section).

 

Examples are: