Comment 6 for bug 1707811

Hi, Is there any update on this issue?

I experienced the same issue on MySQL 5.7.22 (Oracle - community edition), while having the master-master setup. Versions:

root@server:~# mysql --version
mysql Ver 14.14 Distrib 5.7.22, for linux-glibc2.12 (x86_64) using EditLine wrapper

root@server:~# xtrabackup --version
xtrabackup version 2.4.11 based on MySQL server 5.7.19 Linux (x86_64) (revision id: b4e0db5)

Query used:
$XTRABACKUP --defaults-file=$DEFAULTS_FILE --login-path=xtrab --compress --compress-threads=1 --encrypt-threads=1 --parallel=2 --target-dir="$BACKUP_DIR/$DATE" --encrypt=AES256 --encrypt-key-file=$encryption_key_file --backup --history 2> "$BACKUP_LOG/$DATE/Xtra-backup-progress.log"

What happens:
1) It creates the schema PERCONA_SCHEMA
2) It creates an empty table with no records.
3) After running the xtrabackup (full backup), it does not create any entry into the table.

mysql> use PERCONA_SCHEMA
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> show tables;
+--------------------------+
| Tables_in_PERCONA_SCHEMA |
+--------------------------+
| xtrabackup_history |
+--------------------------+
1 row in set (0.00 sec)

mysql> select uuid, start_time, end_time, incremental, compact, compressed, encrypted from PERCONA_SCHEMA.xtrabackup_history order by start_time desc;
Empty set (0.00 sec)