xtrabackup_checkpoints has the wrong format in the 1.3-148.lucid.5_amd64 build

[Will Bryant]

After trying xtrabackup_1.3-148.lucid.5_amd64.deb I found that the xtrabackup_checkpoints file created by innobackupex-1.5.1 looked like this:

backup_type = full-backuped
from_lsn = 0:0
to_lsn = 129:3685934508

However this did not work when I tried to use the same package's xtrabackup to do an incremental backup:

xtrabackup: error: failed to read metadata from /var/backups/mysql/xtrabackup/latest/2010-10-06_16-04-41-full/xtrabackup_checkpoints

I have downgraded to xtrabackup_1.2-132.karmic.15_amd64.deb, whose innobackupex-1.5.1 produces xtrabackup_checkpoints files that look like this:

backup_type = full-backuped
from_lsn = 0
to_lsn = 557824104081

xtrabackup then works properly.

So this seems to be a regression in the 1.3 beta. Did INNODB_VERSION_SHORT change?

[Jeremy Andrews (jeremy-tag1consulting)]

This bug appears to still be present in the latest stable 1.4 release, as well as the latest release candidate, 1.5 (testing with xtrabackup-1.5-9.rhel5.x86_64.rpm).

I installed the older 1.2 release at which incremental backups work as documented, however I think run into errors restoring them, where it reports:
101230 17:16:12 InnoDB: Operating system error number 2 in a file operation. InnoDB: The error means the system cannot find the path specified. xtrabackup: Warning: cannot open 1200-incremental/xtrabackup_logfile. will try to find.
101230 17:16:12 InnoDB: Operating system error number 2 in a file operation. InnoDB: The error means the system cannot find the path specified. xtrabackup: Fatal error: cannot find 1200-incremental/xtrabackup_logfile. xtrabackup: Error: xtrabackup_init_temp_log() failed.

This is reported in spite of the fact that the file does indeed exist at the path specified. In short, I have found incrementals broken in one way or another in 1.2, 1.4, and 1.5.

Is there a plan to get Incremental Backups working before the next release? Do you require any additional debug detail to get this working?

[Vadim Tkachenko (vadim-tk)]

Assigned to Valentine to generate test case

[Valentine Gostev (longbow)]

Will,

it looks like you are using MySQL or Percona Server 5.0, where LSN is two 32-bit numbers.

xtrabackup_1.3-148.lucid.5_amd64.deb is shipped with two binaries: xtrabackup (used for MySQL 5.1+) and xtrabackup_50 (for 5.0). When you issue innobackupex to create a backup it detects that it has been used against 5.0 and uses xtrabackup_50 to create a backup. That's why xtrabackup fails to read meta-data. Please try to perform an incremental backup with xtrabackup_50.

Jeremy,

xtrabackup v. 1.4 and 1.5 provide xtrabackup_51 binary (instead of xtrabackup_50 in v. 1.3). Situation is the same: if you used innobackupex for 5.0, then try incremental backup with xtrabackup_51 - it should work fne.

Since XtraBackup 1.4 xtrabackup_51 binary is used for backups of MySQL 5.0, Percona Server 5.0 and MySQL 5.1 with builtint InnoDB. xtrabackup for 5.1 with InnoDB pluing and 5.5

[Vadim Tkachenko (vadim-tk)]

Assigned to Fred to make documentation more clear on incremental backup

[Fred Linhoss (fred-linhoss)]

Documentation changes:
Pages changed:
http://www.percona.com/docs/wiki/percona-xtrabackup:xtrabackup:start
http://www.percona.com/docs/wiki/percona-xtrabackup:xtrabackup:prepare

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-286