That initial implementation for MariaDB missed the "FLUSH ENGINE LOGS" ordering I have been attempting to fix here - that is a subtle race condition that I assume was simply overlooked at the time.
I am not aware of any present or planned MariaDB equivalent feature to the MySQL 5.7 mysql.gtid_executed table that might avoid needing to copy around these binlogs. Perhaps someone else will be able to comment in that regard.
Yes, the last binary log needs to be copied for similar reasons as MySQL 5.6. That's why this feature was implemented some time ago here:
https:/ /bugs.launchpad .net/percona- xtrabackup/ +bug/1329539
https:/ /github. com/percona/ percona- xtrabackup/ commit/ 60f9795cdbb7ae1 3a554f8cadcb48b cb2a5e3a9d
That initial implementation for MariaDB missed the "FLUSH ENGINE LOGS" ordering I have been attempting to fix here - that is a subtle race condition that I assume was simply overlooked at the time.
I am not aware of any present or planned MariaDB equivalent feature to the MySQL 5.7 mysql.gtid_executed table that might avoid needing to copy around these binlogs. Perhaps someone else will be able to comment in that regard.