MySQL backup -- common errors in xtrabackup backup

1、DDL Operation and Xtrabackup Backup conflict

When MySQL Use xrabckup When doing a backup , If you execute DDL Modify the table , It can lead to xrabckup Backup failed .

Errors are similar to ：

Log in and copy

       

        InnoDB: Last flushed lsn: 3375345258517 load_index lsn 3379255303757
        
InnoDB: An optimized (without redo logging) DDLoperation has been performed. All modified pages may not have been flushed to the disk yet. 
        
PXB will not be able take a consistent backup. Retry the backup operation
       
       

        
1.
        
2.
        
3.
       

2、 Poor disk performance leads to xtrabckup Backup failed

Innodb Logs are generated much faster than Xtrabackup The speed of replication , part Innodb Log truncated , Causes the backup to fail .

Errors are similar to ：

Log in and copy

       

        xtrabackup: error: log block numbers mismatch:
        
xtrabackup: error: expected log block no. 201901064, but got no. 208192508 from the log file.
        
xtrabackup: error: it looks like InnoDB log has wrapped around before xtrabackup could process all records due to either log copying being too slow, or  log files being too small.
        
xtrabackup: Error: xtrabackup_copy_logfile() failed.
       
       

        
1.
        
2.
        
3.
        
4.