using the wrong xtrabackup binary for incremental backups could give a better error

Bug #788316 reported by Kenny Gryp
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to
Fix Released
Alexey Kopytov
Won't Fix
Won't Fix
Fix Released
Alexey Kopytov

Bug Description

when taking an incremental backup with the wrong xtrabackup binary, you can get:

xtrabackup_checkpoints contents:
backup_type = full-backuped
from_lsn = 0:0
to_lsn = 186:2154619219
last_lsn = 186:2183096018

This person tried to run 'xtrabackup --backup --increment...' instead of 'xtrabackup_51 --backu...' and got this error:
xtrabackup: error: failed to read metadata from /root/db_backup/2011-05-25_12-45-00/xtrabackup_checkpoints

This is a xtrabackup_checkpoints file created with xtrabackup_51 (probably invoked through innobackupex which makes it more confusing) and does not work with 'xtrabackup'.

It would be better if the error displayed would also mention to use the correct xtrabackup binary.
I had several questions on freenode#percona related to this.

related doc:

Related branches

Changed in percona-xtrabackup:
importance: Undecided → Wishlist
status: New → Opinion
assignee: nobody → Valentine Gostev (longbow)
Changed in percona-xtrabackup:
status: Opinion → New
Changed in percona-xtrabackup:
importance: Wishlist → Low
status: New → Confirmed
Stewart Smith (stewart)
Changed in percona-xtrabackup:
status: Confirmed → Triaged
assignee: Valentine Gostev (longbow) → nobody
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to:

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.