Bug #57286 --apply-log is not updating binlog/lsn info files in full backup dir

• Submitted: 6 Oct 2010 14:24
• Modified: 28 Jan 2011 0:29
• Reporter: Victor Kirkebo
• Status: Closed
• Category: MySQL Enterprise Backup
• Severity: S3 (Non-critical)
• Version: 3.5
• OS: Any
• Assigned to: Satya B
• CPU Architecture: Any

[6 Oct 2010 14:24] Victor Kirkebo

Description:
When a backup is done two files are generated in the backup directory.
The files contain information about the backup's binlog position and lsn.
The files are:
1) ibbackup_binlog_info
2) ibbackup_export_variables.txt

When you run a full backup and later an incremental backup you will have two sets of these files - one in the full backup directory and one in the incremental backup directory. If you apply the incremental backup towards the full backup the info files (ibbackup_binlog_info and ibbackup_export_variables.txt) in the full backup directory are not updated.

As part of the process of applying the incremental log I think the info files should be copied from the incremental backup directory to the full backup directory in order to reflect the updated binlog pos and lsn of the full backup.

How to repeat:
Run a full backup and read the files ibbackup_binlog_info and ibbackup_export_variables.txt in the full backup directory

Run an incremental backup and read the files ibbackup_binlog_info and ibbackup_export_variables.txt in the incremental backup directory

Apply the incremental backup towards the full backup.
Verify that the files ibbackup_binlog_info and ibbackup_export_variables.txt in the full backup directory have not changed.

[12 Oct 2010 5:44] Satya B

The problem is in mysqlbackup applylog() implementation, which doesn't copy these files. 

Soon to be fixed

[21 Oct 2010 12:48] Omer Barnir

triage: setting to EB35MRU (assuming impact is low (only missing from the files)

[3 Nov 2010 9:26] Satya B

Sanjay,

plz assign reviewers for this bug.

[4 Nov 2010 9:01] Ingo Strüwing

Approved pending changes. Please see email.

[8 Nov 2010 7:09] Satya B

revno: 251
revision-id: [e-mail]-20101108064924-s7x8gj6bnwqqcntw
parent: [e-mail]-20101029120245-oooutb27w3yp30ut

[2 Dec 2010 9:13] Satya B

This doesn't affect upgrade.

In 3.5.1, the binlog info file "ibbackup_binlog_info" file in full backup directory is not updated when an incremental backup is applied(--apply-log operation) to the full backup.

In 3.5.2, the above problem is fixed and updates the ibbackup_binlog_info file in the fullbackup directory when we apply incremental backup to full backup during --apply-log operation.

In addition, it also updates the ibbackup_export_variables.txt which is introduced in 3.5.2

I am not sure if it deserves a changelog entry or not. 

Atleast there is a change from 3.5.1 to 3.5.2 w.r.t to updating the 'ibbackup_binlog_info" file.

[28 Jan 2011 0:29] John Russell

Added to 3.5.2 change log:

The file ibbackup_binlog_info in the backup directory is now updated
when an incremental backup is applied, to reflect the updated binlog
position and LSN of the full backup.