We’re using Percona’s innobackupex version v1.5.1-xtrabackup with xtrabackup version 2.2.8.
At some point the from restored backups contains only the GTID and not the binary log filename and position as it used to:
backups-01:/restore/full# cat xtrabackup_binlog_info 62397e9e-981c-11e3-a2bf-02011441b742:1-435590
This makes a lot harder to restore to a point in time using parameter to be a binary log position to begin replaying the SQL statements from there.
The only workaround that I found is to use to dump the initial binary log file and manually search for the next GTID, taking its starting log poisition.
Is this expected or should I fill a bug report? Is there a way to make the point-in-time recovery straightforward with only the starting GTID at hand?
Thanks in advance,