Is this a bug of Xtrabackup 8.0.23-16 and MySQL 8.0.23,when I executed --copy-back, there was an error in the index file of binlog

MySQL & MariaDB Percona XtraBackup
1

Xtrabackup version：8.0.23-16
MySQL version ：8.0.23 Community

my.cnf include the following information about：

[root@192 data]# cat /etc/my.cnf |grep 'log-bin\|datadir'
datadir	= /data/mysql
log-bin = /data/mysql/mybinlog

1.do backup

2.do prepare
prepare is ok ， and I get the following values like :

[root@192 backup]# cat xtra_full_20210515160208/mybinlog.index
/data/mysql/mybinlog.000005
  1. copy-back
xtrabackup --defaults-file=/etc/my.cnf --copy-back --target-dir=/data/backup/xtra_full_20210515160208/

When I finished executing --copy-back, I found that there was a problem,The index file of binlog is missing some information，When I change it to mybinlog.000005，MySQL can be started normally。

[root@192 ~]# cat /data/mysql/mybinlog.index 
/data/mysql/.000005
1 Like
2

thanks @yangdada for reporting. We have verified it as bug.
The workaroud is by avoiding the absolute path in log-bin. just use filename if possible.

1 Like
3

you can track [PXB-2510] copy-back is not restoring binlog file properly when absolute path in used in log-bin - Percona JIRA to know to progress on this bug.

1 Like