xtrabackup_binlog_info is not being updated correctly when applying incrementals

[Agustín]

Xtrabackup (innobackupex) 2.3 is not correctly updating binlog position in xtrabackup_binlog_info after applying the logs to an incremental backup; but it is correctly updating the xtrabackup_binlog_pos_innodb file.

Xtrabackup (innobackupex) 2.2 behaves differently, though. It updates the xtrabackup_binlog_info correctly, but deletes xtrabackup_binlog_pos_innodb when applying logs for an incremental.

I will attach 2 files with outputs for 2.3 and 2.2 versions.

Agustín.

[Agustín (agustin-gallego)]

Outputs for tests with xtrabackup 2.2.13

[Agustín (agustin-gallego)]

Outputs for tests with xtrabackup 2.3.2

[Sergei Glushchenko (sergei.glushchenko)]

I think the issue is xtrabackup_binlog_info is copied over from incremental directory in 2.2, but is not copied in 2.3

[Sergei Glushchenko (sergei.glushchenko)]

https://github.com/percona/percona-xtrabackup/pull/139

[Sergei Glushchenko (sergei.glushchenko)]

https://github.com/percona/percona-xtrabackup/pull/140

[Doug Shelley (0-doug)]

I'm running MariaDB 10.0.23 on RHEL 7.1. I have PXB 2.3.3-1. I seem to still have this issue - when I restore parent/incremental vi PXB, the restore database doesn't have the xtrabackup_binlog_info in it.

Attached are the innobackup.log (from master) and innoprepare.log (from slave).

[Sergei Glushchenko (sergei.glushchenko)]

The log you uploaded is from final prepare (without specifying incremental dir and without --redo-only). When you run

innobackupex --apply-log --redo-only BASE-DIR --incremental-dir=INCREMENTAL-DIR-1

you should see something like

160122 11:48:52 [00] Copying INCREMENTAL-DIR-1/xtrabackup_info to ./xtrabackup_info

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-448