Binary log position does not match in apply-log output during backup-and-apply-log (Doc ID 1529035.1)

Last updated on JUNE 16, 2016

Applies to:

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

Symptoms

 When executing backup-and-apply-log output on binary log, the position does not match the binary log position recorded in meta/backup_variables.txt.

Starting from MySQL Enterprise Backup 3.6 a new meta subdirectory inside the backup data contains information about the backup itself.
This metadata is known collectively as the manifest.

An example output of backup-and-apply-log about binary log position.
mysqlbackup: INFO: Last MySQL binlog file position 0 220002, file name
./localhost-bin.000001

However if you look at the binary log position in backup_variables.txt file the value will be
slightly bigger.
(Output taken from MySQL Enterprise Backup 3.8.1)  
binlog_position=localhost-bin.000001:224000

This could cause data inconsistency if user tries to pick the wrong binary log position value in backup_variables.txt
for point in time recovery.

Affected MySQL Enterprise Backup version are 3.8.0 and 3.8.1. However this issue was fixed and merged in MySQL Enterprise Backup 3.8.2.

 

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