innobackupex continuing with FTWRL even when xtrabackup failed
>> log scanned up to (300606271182)
xtrabackup: error: log block numbers mismatch:
xtrabackup: error: expected log block no. 587121624, but got no. 587142096 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_
130418 01:35:49 innobackupex: Continuing after ibbackup has suspended
130418 01:35:49 innobackupex: Starting mysql with options: --defaults-
130418 01:35:49 innobackupex: Connected to database with mysql child process (pid=15080)
130418 01:35:51 innobackupex: Starting to lock all tables...
130418 01:36:05 innobackupex: All tables locked and flushed to disk
130418 01:36:05 innobackupex: Starting to backup non-InnoDB tables and files
innobackupex: in subdirectories of '/var/lib/mysql'
innobackupex: Backing up files '/var/lib/
In this case there are thousands of databases and millions of .frm files, so the FTWRL was held for 2 hours before the backup ultimately failed anyway.
Note the user has 5M log files (default), hence the xtrabackup failure.
This was 2.0.4, so I'm not 100% sure this isn't already fixed, but I figured I'd file anyway.
- innobackupex continuing with FLTWRL even when xtrabackup failed
+ innobackupex continuing with FTWRL even when xtrabackup failed