MySQL Bugs: #70475: MEB 3.9 fails during apply-incremental-backup on full backup

Bug #70475	MEB 3.9 fails during apply-incremental-backup on full backup
Submitted:	1 Oct 2013 14:26	Modified:	8 Nov 2013 18:41
Reporter:	DB Support	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Enterprise Backup	Severity:	S2 (Serious)
Version:	3.9	OS:	Linux
Assigned to:		CPU Architecture:	Any
Tags:	Backup, commercial, Enterprise, meb, MySQL

Description:
Applying a incremental backup on full backup using the next command:

/opt/mysql/enterprise/meb-3.9/bin/mysqlbackup --protocol=tcp --user=mysql --password=xxxxxx --incremental-backup-dir=/opt/mysql/backup/incremental/2013-10-01_15-38-21 --backup-dir=/opt/mysql/backup/full/2013-10-01_15-26-19  apply-incremental-backup

Get:
 mysqlbackup: INFO: Creating 14 buffers each of size 65536.
131001 15:52:37 mysqlbackup: INFO: Apply-log operation starts with following threads
		1 read-threads    1 process-threads
131001 15:52:39 mysqlbackup: INFO: ibbackup_logfile's creation parameters:
          start lsn 534760316928, end lsn 534760385835,
          start checkpoint 534760316999.
 mysqlbackup: INFO: Backup was originally taken with the --include regexp option
InnoDB: Doing recovery: scanned up to log sequence number 534760385835
 mysqlbackup: INFO: InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74  mysqlbackup: ERROR: Signal 11 received.
stack_bottom = 0 thread_stack 0x10000
/opt/mysql/enterprise/meb-3.9/bin/mysqlbackup(my_print_stacktrace+0x35)[0x4f9835]
/opt/mysql/enterprise/meb-3.9/bin/mysqlbackup(_ZN3meb9ExceptionC2ENS_18enum_error_numbersEPKcS3_i+0x73)[0x440723]
/opt/mysql/enterprise/meb-3.9/bin/mysqlbackup(_ZN3meb4util14handle_signalsEi+0x10f)[0x44b33f]
/lib64/libpthread.so.0[0x359100f500]
/opt/mysql/enterprise/meb-3.9/bin/mysqlbackup[0x57d9ef]
/opt/mysql/enterprise/meb-3.9/bin/mysqlbackup[0x57a679]
/opt/mysql/enterprise/meb-3.9/bin/mysqlbackup[0x57aca6]
/opt/mysql/enterprise/meb-3.9/bin/mysqlbackup[0x573edc]
/opt/mysql/enterprise/meb-3.9/bin/mysqlbackup[0x575958]
/opt/mysql/enterprise/meb-3.9/bin/mysqlbackup[0x575cb5]
/opt/mysql/enterprise/meb-3.9/bin/mysqlbackup(_ZN3meb14Back_apply_log8completeEv+0x2f)[0x42c6df]
/opt/mysql/enterprise/meb-3.9/bin/mysqlbackup(_ZN3meb9Processor3runEv+0x25a)[0x4cea3a]
/opt/mysql/enterprise/meb-3.9/bin/mysqlbackup(_ZN3meb6Thread11startThreadEPv+0x23)[0x4dd3c3]
/lib64/libpthread.so.0[0x3591007851]
/lib64/libc.so.6(clone+0x6d)[0x35908e767d]

Full backup was done with:
$DIR_BIN/mysqlbackup --host=$HOST --port=$PORT --protocol=tcp --user=$USER --password=$PASS --only-innodb-with-frm=all --compress --compress-level=$LEVEL --skip-unused-pages --include='*/.*.*|^iceRuntimeLog.log' --on-disk-full=abort_and_remove --backup-dir=$DIR_BACK/full --with-timestamp backup-to-image --backup-image=mysqldb.$DATE

Incremental backup was done with:
$DIR_BIN/mysqlbackup --host=$HOST --port=$PORT --protocol=tcp --user=$USER --password=$PASS --only-innodb-with-frm=all --backup-dir=$DIR_BACK/incremental --include='*/.*.*|^iceRuntimeLog.log' --on-disk-full=abort_and_remove --with-timestamp backup-to-image --backup-image=mysqldb.$DATE --incremental  --start-lsn=$LSN_NUMBER 

Backup restore was performed with:
/opt/mysql/enterprise/meb-3.9/bin/mysqlbackup --defaults-file=/etc/my.cnf --backup-dir=/opt/mysql/backup/full/2013-10-01_15-26-19 --backup-image=mysqldb.20131001_152618 image-to-backup-dir

/opt/mysql/enterprise/meb-3.9/bin/mysqlbackup --defaults-file=/etc/my.cnf --backup-dir=/opt/mysql/backup/full/2013-10-01_15-26-19 apply-log --uncompress

>> /opt/mysql/enterprise/meb-3.9/bin/mysqlbackup --protocol=tcp --user=mysql --password=omega --incremental-backup-dir=/opt/mysql/backup/incremental/2013-10-01_15-38-21 --backup-dir=/opt/mysql/backup/full/2013-10-01_15-26-19  apply-incremental-backup
 
>>> FAILED with core dump

How to repeat:
Mysql Commercial edition 5.6.10
MEB 3.9

/etc/my.cnf
[mysqld]
server-id=1
large-pages
host_cache_size=0
explicit_defaults_for_timestamp=true
port=3306
max_connections=1000
max_prepared_stmt_count=1000000
wait_timeout=31536000
interactive_timeout=31536000

datadir='/opt/mysql/data'

# Innodb
innodb_file_per_table
innodb_support_xa=1
innodb_data_home_dir='/opt/mysql/data/innodb'
innodb_data_file_path=ibdata1:10M:autoextend
innodb_log_files_in_group=5
innodb_log_group_home_dir='/opt/mysql/redolog'
innodb_buffer_pool_size=16G
innodb_log_file_size=1G
innodb_log_buffer_size=512M
innodb_flush_log_at_trx_commit=1
innodb_lock_wait_timeout=50
innodb_undo_directory='/opt/mysql/data/undo'
innodb_undo_tablespaces=10
innodb_strict_mode=ON
sync_binlog=1

binlog-format=row
sync-binlog=1
log-bin=/opt/mysql/data/binlog/bin-log

character_set_server='latin1'     

log_error='/var/log/mysql/mysql_error.log'
user=mysql

Suggested fix:
None

If mysqlbackup output directory contains another files outside the backup, apply-incremental-backup fails.

We considered to perform a backup throught meb 3.9, mysqldump and "cp" of MyASM files and including all files in MEB 3.9 output directory to recover a partial but consistent backup.

Thank you for the report.

Please upload core dump which apply-incremental-backup created.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".