My Oracle Support Banner

Missing Last MySQL Binlog File Position In Mysql Enterprise Backup (MEB) 3.10 or 3.11 (Doc ID 2179450.1)

Last updated on SEPTEMBER 11, 2016

Applies to:

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

Symptoms

Last MySQL binlog file position will not be presented in the logs when using MySQL Enterprise Backup version 3.10 or 3.11 with --no-locking option.

 

Examples are:

# mysqlbackup --no-locking --backup-dir=/bak --with-timestamp --protocol=tcp --user=root --host=localhost -p backup

mysqlbackup: INFO: We were able to parse ibbackup_logfile up to
lsn 1626134.
mysqlbackup: INFO: The first data file is '/bak/2016-09-05_11-10-43/datadir/ibdata1'
and the new created log files are at '/bak/2016-09-05_11-10-43/datadir'
mysqlbackup: INFO: Apply-log operation completed successfully.
mysqlbackup: INFO: Full backup prepared for recovery successfully.

mysqlbackup completed OK!

 

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.