Xtrabackup_binlog_pos_innodb and Xtrabackup_binlog_info

The person who backs up the data using the Xtrabackup tool's Innobackupex script may notice that there are two files in the backup data processed by –apply-log that indicate the file name and location of the binlog that the backup data corresponds to. But sometimes the location of the two files may be different.
After experimenting and inquiring Percona company, the conclusion is as follows:
1 for Pure InnoDB operation, the contents of the above two files in the backed up data are consistent
2 for InnoDB and non-transactional storage engine blending operations, the position shown in Xtrabackup_binlog_info should be larger than the values shown in Xtrabackup_pos_innodb. The xtrabackup_binlog_info shall prevail at this time, and the contents shown in the recovery log of the latter and Apply-log are consistent and only for the InnoDB data

In addition, today found Innobase/mysql/oracle company produced by the MySQL Enterprise Backup (original InnoDB hot backup) innobackup script back up the data also has a similar problem. This is actually due to the time difference between the InnoDB table and the non-transactional table when the hot copy is copied.

Xtrabackup_binlog_pos_innodb and Xtrabackup_binlog_info