Bug #64952 Full backup becomes incremental after power loss
Submitted: 12 Apr 2012 10:35 Modified: 5 Mar 2013 12:39
Reporter: Sveta Smirnova Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Backup Severity:S3 (Non-critical)
Version:3.8.0 OS:Any
Assigned to: CPU Architecture:Any

[12 Apr 2012 10:35] Sveta Smirnova
Description:
Created from http://forums.mysql.com/read.php?28,522669,525048#msg-525048

After power loss during apply-backup-incremental operation backup_variables.txt file in the full backup meta directory contains "is_incremental=1", thus all following tries to apply incremental backup fail with:

 mysqlbackup: ERROR: The apply-incremental-backup operation encountered
      incremental backup snapshot directory in place of
      full backup.

How to repeat:
1. Create a full backup
2. Create incr backup
3. Apply log to full backup
3. Apply incr to full
4. Create another incr backup
5. Apply incr to full; kill -9 before it finishes
6. The full backup is now corrupt. 

Output of following try to apply incremental backup:

[sveta@delly meb-trunk]$ ./bin/mysqlbackup  --backup-dir=/home/sveta/src/BACKUPDIR/LS_full --incremental-backup-dir=/home/sveta/src/BACKUPDIR/LS_incr2 apply-incremental-backup
MySQL Enterprise Backup version 3.8.0 [2012/03/22] 
Copyright (c) 2003, 2012, Oracle and/or its affiliates. All Rights Reserved.

INFO: Starting with following command line ...
 ./bin/mysqlbackup --backup-dir=/home/sveta/src/BACKUPDIR/LS_full 
        --incremental-backup-dir=/home/sveta/src/BACKUPDIR/LS_incr2 
        apply-incremental-backup 

IMPORTANT: Please check that mysqlbackup run completes successfully.
            At the end of a successful 'apply-incremental-backup' run mysqlbackup
            prints "mysqlbackup completed OK!".

 mysqlbackup: ERROR: The apply-incremental-backup operation encountered
      incremental backup snapshot directory in place of
      full backup.

Content of backup_variables.txt:

[sveta@delly mysql-test]$ cat /home/sveta/src/BACKUPDIR/LS_incr1/meta/backup_variables.txt 
#
# This file is auto generated by mysqlbackup.
#
[backup_variables]
start_lsn=519467856
end_lsn=519484257
apply_log_done=0
is_incremental=1
is_incremental_with_redo_log_only=0
is_partial=0
is_compressed=0
is_onlyinnodb=0
[28 Feb 2013 15:52] Sanjay Manwani
Backup team was able to reproduce the failing incremental apply-log operation as
described above. But was also able to repair the backup by issuing
incremental apply-log with --force option.
So, we did not find any bug in the incremental apply-log.