Incremental restore removes myisam tables

Bug #1508561 reported by higuita
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Expired
Undecided
Unassigned

Bug Description

i have one full backup and several incremental backups

when i do a restore i do this:

innobackupex --apply-log --redo-only /var/restore/full/
for i in inc1 inc2 inc3 inc4 inc5 ; do
  innobackupex --apply-log --redo-only /var/restore/full/ --incremental-dir="/var/restore/$i/"
done
innobackupex --apply-log /var/restore/full/ --incremental-dir="/var/restore/inc6/"
innobackupex --apply-log /var/restore/full/
innobackupex --copy-back /var/restore/full/
chown -R mysql:mysql /var/lib/mysql/

All works well and i have the innodb tables in the /var/lib/mysql/, yet trying to start the DB complains that the mysql/ database is missing tables. Checking i can see that the mysql/ directory only have this:
gtid_slave_pos.ibd
innodb_index_stats.ibd
innodb_table_stats.ibd

Checking the /var/restore/full/ , the mysql/ directory is now empty, but it had the myisam tables in the original backup. Also, all incremental backups also have the myisam tables.

I have repeated the process and i notice that after applying the first incremental, the myisam tables disappear.
the documentation in https://www.percona.com/doc/percona-xtrabackup/2.1/innobackupex/incremental_backups_innobackupex.html reports that the myisam would be copied in each incremental, but this is not happening.

If i manually copy the myisam tables from the last incremental to the correct location, the mysql starts fine and everything works.

So, unless i'm doing something wrong, innobackupex is not copying the myisam tables as the documentation reports and there is a bug in the tool, or in the documentation :)

i'm using this version on debian jessie:
   percona-xtrabackup 2.2.12-1.jessie

innobackupex reports this:

  $ innobackupex --version
InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.

This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.

Get the latest version of Percona XtraBackup, documentation, and help resources:
http://www.percona.com/xb/p

Thanks in advance for the help and for the great backup tool
higuita

Revision history for this message
Sergei Glushchenko (sergei.glushchenko) wrote :

I am unable to reproduce

I am using exactly this script:

innobackupex --no-timestamp $topdir/full/
innobackupex --no-timestamp --incremental --incremental-basedir=$topdir/full/ $topdir/inc1/
innobackupex --no-timestamp --incremental --incremental-basedir=$topdir/inc1/ $topdir/inc2/
innobackupex --no-timestamp --incremental --incremental-basedir=$topdir/inc2/ $topdir/inc3/
innobackupex --no-timestamp --incremental --incremental-basedir=$topdir/inc3/ $topdir/inc4/
innobackupex --no-timestamp --incremental --incremental-basedir=$topdir/inc4/ $topdir/inc5/
innobackupex --no-timestamp --incremental --incremental-basedir=$topdir/inc5/ $topdir/inc6/

innobackupex --apply-log --redo-only $topdir/full/
for i in inc1 inc2 inc3 inc4 inc5 ; do
  innobackupex --apply-log --redo-only $topdir/full/ --incremental-dir="$topdir/$i/"
done

innobackupex --apply-log $topdir/full/ --incremental-dir="$topdir/inc6/"
innobackupex --apply-log $topdir/full/

ls $topdir/full/mysql

The output of ls is:

columns_priv.MYD
columns_priv.MYI
columns_priv.frm
db.MYD
db.MYI
db.frm
event.MYD
event.MYI
event.frm
func.MYD
func.MYI
func.frm
general_log.CSM
general_log.CSV
general_log.frm
help_category.MYD
help_category.MYI
help_category.frm
help_keyword.MYD
help_keyword.MYI
help_keyword.frm
help_relation.MYD
help_relation.MYI
help_relation.frm
help_topic.MYD
help_topic.MYI
help_topic.frm
innodb_index_stats.frm
innodb_index_stats.ibd
innodb_table_stats.frm
innodb_table_stats.ibd
ndb_binlog_index.MYD
ndb_binlog_index.MYI
ndb_binlog_index.frm
plugin.MYD
plugin.MYI
plugin.frm
proc.MYD
proc.MYI
proc.frm
procs_priv.MYD
procs_priv.MYI
procs_priv.frm
proxies_priv.MYD
proxies_priv.MYI
proxies_priv.frm
servers.MYD
servers.MYI
servers.frm
slave_master_info.frm
slave_master_info.ibd
slave_relay_log_info.frm
slave_relay_log_info.ibd
slave_worker_info.frm
slave_worker_info.ibd
slow_log.CSM
slow_log.CSV
slow_log.frm
tables_priv.MYD
tables_priv.MYI
tables_priv.frm
time_zone.MYD
time_zone.MYI
time_zone.frm
time_zone_leap_second.MYD
time_zone_leap_second.MYI
time_zone_leap_second.frm
time_zone_name.MYD
time_zone_name.MYI
time_zone_name.frm
time_zone_transition.MYD
time_zone_transition.MYI
time_zone_transition.frm
time_zone_transition_type.MYD
time_zone_transition_type.MYI
time_zone_transition_type.frm
user.MYD
user.MYI
user.frm

Do you see any error messages? Could you maybe provide a list of files in full and first incremental backups?

Changed in percona-xtrabackup:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Percona XtraBackup because there has been no activity for 60 days.]

Changed in percona-xtrabackup:
status: Incomplete → Expired
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

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

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.