# Xtrabackup\_binlog\_info | xtrabackup\_binlog\_pos\_innodb which file is correct for replication?

**URL:** <https://forums.percona.com/t/xtrabackup-binlog-info-xtrabackup-binlog-pos-innodb-which-file-is-correct-for-replication/11576>\
**Category:** Percona XtraBackup\
**Created:** [July 29, 2021, 5:33am UTC](https://forums.percona.com/t/xtrabackup-binlog-info-xtrabackup-binlog-pos-innodb-which-file-is-correct-for-replication/11576 "2021-07-29T05:33:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rkwmt\_ns](https://avatars.discourse-cdn.com/v4/letter/r/958977/32.png) [@rkwmt\_ns](https://forums.percona.com/u/rkwmt_ns)\
**Post date:** [July 29, 2021, 5:33am UTC](https://forums.percona.com/t/xtrabackup-binlog-info-xtrabackup-binlog-pos-innodb-which-file-is-correct-for-replication/11576/1 "2021-07-29T05:33:10Z")

</div>

Let me know which file - xtrabackup\_binlog\_info | xtrabackup\_binlog\_pos\_innodb - is correct for replication.

[Our system construction]

- has 2 database servers : source and replica
- RedHat Enterprise Linux 7
- MySQL 8.0.22-1.el7
- percona-xtrabackup 80-8.0.12-1.el7
- using only InnoDB as storage engine

[Situation]  
I made backup from source server by using xtrabackup and moved to another to make replica.  
At another server, I done prepare \> copy-back \> start mysqld, all steps succeeded.  
But I was confused which file is correct to use for CHANGE MASTER TO query - xtrabackup\_binlog\_info or xtrabackup\_binlog\_pos\_innodb.

I done CHANGE MASTER TO query by contain of xtrabackup\_binlog\_info, it succeeded in replication.  
Otherwise replication failed by using xtrabackup\_binlog\_pos\_innodb.

[Contains of those files]

# cat xtrabackup\_binlog\_info

mysql-bin.000587 156

# cat xtrabackup\_binlog\_pos\_innodb

mysql-bin.000036 871616440

- MASTER STATUS at source mysql when backuping was finished:  
\*\*\* this system is already running and updating data.

> SHOW MASTER STATUS;  
> ±-----------------±---------±-------------±-----------------±------------------+  
> | File | Position | Binlog\_Do\_DB | Binlog\_Ignore\_DB | Executed\_Gtid\_Set |  
> ±-----------------±---------±-------------±-----------------±------------------+  
> | mysql-bin.000587 | 15036 | | | |  
> ±-----------------±---------±-------------±-----------------±------------------+

and the file “mysql-bin.000036” was not exists each servers.

I think xtrabackup\_binlog\_pos\_innodb is not usable for CHANGE MASTER TO query,  
but percona’s document says below:

This output can also be found in the `xtrabackup_binlog_pos_innodb` file, but **it is only correct** when no other than _XtraDB_ or _InnoDB_ are used as storage engines.  
(at [Percona Documentation](https://www.percona.com/doc/percona-xtrabackup/8.0/xtrabackup_bin/working_with_binary_logs.html) )

In my case, xtrabackup\_binlog\_pos\_innodb should be also correct but it contains wrong position.

Should I use xtrabackup\_binlog\_info for Replication?

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [July 29, 2021, 2:59pm UTC](https://forums.percona.com/t/xtrabackup-binlog-info-xtrabackup-binlog-pos-innodb-which-file-is-correct-for-replication/11576/2 "2021-07-29T14:59:46Z")

</div>

Hi @rkwmt_ns,  
Always use `xtrabackup_binlog_info` to be safe. Cheers!

---

<div class="post-metadata">

**Author:** ![Marcelo\_Altmann](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/marcelo_altmann/32/11299_2.png) [@Marcelo\_Altmann](https://forums.percona.com/u/Marcelo_Altmann)\
**Post date:** [July 29, 2021, 3:38pm UTC](https://forums.percona.com/t/xtrabackup-binlog-info-xtrabackup-binlog-pos-innodb-which-file-is-correct-for-replication/11576/3 "2021-07-29T15:38:15Z")

</div>

Hi @rkwmt_ns . To complement what @matthewb said, on the next release of Xtrabackup we will no longer generate xtrabackup\_binlog\_pos\_innodb . The reason is that after MySQL / PS 8.0.17 the server stopped populating correct binlog coordinations to general tablespace, which is where xtrabackup\_binlog\_pos\_innodb read it from. More details at [MySQL Bugs: #104287: trx\_sys binlog coordinates broken after clone plugin](https://bugs.mysql.com/bug.php?id=104287)

You should always use xtrabackup\_binlog\_info.

---

<div class="post-metadata">

**Author:** ![rkwmt\_ns](https://avatars.discourse-cdn.com/v4/letter/r/958977/32.png) [@rkwmt\_ns](https://forums.percona.com/u/rkwmt_ns)\
**Post date:** [July 30, 2021, 1:04am UTC](https://forums.percona.com/t/xtrabackup-binlog-info-xtrabackup-binlog-pos-innodb-which-file-is-correct-for-replication/11576/4 "2021-07-30T01:04:02Z")

</div>

I got it. Thanks for your replay!!

---

<div class="post-metadata">

**Author:** ![rkwmt\_ns](https://avatars.discourse-cdn.com/v4/letter/r/958977/32.png) [@rkwmt\_ns](https://forums.percona.com/u/rkwmt_ns)\
**Post date:** [July 30, 2021, 1:05am UTC](https://forums.percona.com/t/xtrabackup-binlog-info-xtrabackup-binlog-pos-innodb-which-file-is-correct-for-replication/11576/5 "2021-07-30T01:05:50Z")

</div>

Thank for your information. I will check it out!