# infinite "log scanned up to" on backup

**URL:** <https://forums.percona.com/t/infinite-log-scanned-up-to-on-backup/6682>\
**Category:** Percona XtraBackup\
**Created:** [November 14, 2018, 3:56am UTC](https://forums.percona.com/t/infinite-log-scanned-up-to-on-backup/6682 "2018-11-14T03:56:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Futureweb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/futureweb/32/1034_2.png) [@Futureweb](https://forums.percona.com/u/Futureweb)\
**Post date:** [November 14, 2018, 3:56am UTC](https://forums.percona.com/t/infinite-log-scanned-up-to-on-backup/6682/1 "2018-11-14T03:56:01Z")

</div>

Hello,  
I got something suspicious with my backups. They were ok for several years now - but the last weeks they gone mad. Instead of finishing within ~30 Minutes - they run over 24 Hours now with hundred-thousands of those Messages:

…  
181114 05:07:57 Starting prep copy of non-InnoDB tables and files  
181114 05:07:57 Starting rsync as: rsync -t . --files-from=/tmp/xtrabackup\_rsyncfiles\_pass1 /backup/daten/mysql-0/innobackupex/  
181114 05:07:58 rsync finished successfully.  
181114 05:07:58 Finished a prep copy of non-InnoDB tables and files  
181114 05:07:58 Executing FLUSH NO\_WRITE\_TO\_BINLOG TABLES…  
…  
181114 09:29:44 \>\> log scanned up to (28955061797012)  
181114 09:29:45 \>\> log scanned up to (28955061797012)  
181114 09:29:46 \>\> log scanned up to (28955061797012)  
181114 09:29:47 \>\> log scanned up to (28955061797012)  
181114 09:29:48 \>\> log scanned up to (28955061797012)  
…

Can’t find what’s causing this Problem … maybe one of you got an idea? 😉

MariaDB 10.1.35 on Centos 7.5.1804:  
Using server version 10.1.35-MariaDB  
innobackupex version 2.3.10 based on MySQL server 5.6.24 Linux (x86\_64) (revision id: bd0d4403f36)

thx, bye from Austria  
Andreas Schnederle-Wagner

---

<div class="post-metadata">

**Author:** ![professortrex](https://avatars.discourse-cdn.com/v4/letter/p/e56c9b/32.png) [@professortrex](https://forums.percona.com/u/professortrex)\
**Post date:** [March 8, 2019, 4:26pm UTC](https://forums.percona.com/t/infinite-log-scanned-up-to-on-backup/6682/2 "2019-03-08T16:26:35Z")

</div>

I had the same issue last night. Normally, the “Executing FLUSH NO\_WRITE\_TO\_BINLOG TABLES” command finishes in \<1s, last night it ran for 3 hours until manual abort. It printed out the “log scanned up to ()” lines.