Xtrabackup endless loop of log scanned up to

MySQL & MariaDB Percona XtraBackup
1

Hi since last night the backup on one of myserver never finish and is stuck in a endless loop of thoses messages :
210415 02:17:04 >> log scanned up to (3820614633)
210415 02:17:05 >> log scanned up to (3820614633)
210415 02:17:06 >> log scanned up to (3820614633)
210415 02:17:07 >> log scanned up to (3820614633)

The version of Percona Server ans xtrabackup are :
/bin/xtrabackup version 8.0.14 based on MySQL server 8.0.21 Linux (x86_64) (revision id: 113f3d7)

1 Like
2

@simon.tardif

Typically “log scanned up to” does not stuck and usually it waits on process that copies files.
Do you have huge files to copy? Were there IO errors on the source or destination device?

Also you can try the newer version of Percona XtraBackup

1 Like
3

yesterday users inserted a lot of data and one table is now 72gb maybe that’s the problem? How can we get it to run faster ?

1 Like
4

Hi @simon.tardif. The speed of xtrabackup is determined by the speed of your disks. You cannot magically make something “go faster” if you don’t have the capacity. Why kind of disks do you have? Do you have any monitoring of the disk IO/latency? Have you looked at CPU await time?

1 Like
5

hi yes maybe the nfs where we store the backup is not fast enough. I will check with storage team for this.
Thanks for your answer

1 Like
6

Hi @matthewb could it be because one of the table is 72Gb and is MyIsam? Also she seems to be almost always used?

1 Like
7

@simon.tardif Ah, yes. We assume that if you are using MySQL 8.0 (or even 5.7) that all of your tables are InnoDB as MyISAM is a dead engine. You really should consider converting this table to InnoDB. Yes, while this MyISAM table is being copied, you will not see any progress on InnoDB’s log sequence (log scanned up to) because they are different engines. But, InnoDB must continue to be monitored so that your backup is consistent across all engines.

Absolutely convert all tables to InnoDB, and then ditch the NFS and instead use the streaming option built-in to xtrabackup to send the backup over netcat or ssh directly to your backup server.

2 Likes
8

Ok thank you again for your answer.

1 Like
9

HI we converted everything to innodb but backup always fails with an error like that :
xtrabackup: Can’t create/write to file ‘/mnt/mysql/filename.ibd.xbcrypt’ (OS errno 17 - File exists)
encrypt: ds_open(“filename.ibd.xbcrypt”) failed.
When I start the backup the directory is empty
 I don’t understand why it happens
 do you have an idea ?
It’s not always the same file in the message

1 Like
10

I would check any mount permissions, try running xtrabackup with sudo, put selinux into permissive, etc.

1 Like