MySQL Bugs: #26721: innobackup does not copy .TRN and .TRG files

Bug #26721	innobackup does not copy .TRN and .TRG files
Submitted:	28 Feb 2007 14:52	Modified:	11 Jan 2008 18:31
Reporter:	Elan Ruusamäe (OCA)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S1 (Critical)
Version:	1.3.0	OS:	Any
Assigned to:	Pekka Lampio	CPU Architecture:	Any
Tags:	ibbackup, innobackup

Description:
innobackup (http://www.innodb.com/manual.php#innobackup) does not copy trigger information tables when creating snapshot, which causes loss of data.

trigger data is stored in database dir in .TRN and .TRG files.

How to repeat:
0. create database with triggers.
1. install ibbackup (evaluation version is ok) / innobackup from
http://www.innodb.com/order.php and http://www.innodb.com/manual.php#innobackup
2. run backup, ie:
# innobackup /etc/mysql/mysqld.conf --no-timestamp /var/tmp/innobackup
3. restore backup, ie:
# innobackup --apply-log /var/tmp/innobackup/backup-my.cnf /var/tmp/innobackup/
# mysqld --defaults-file=/var/tmp/innobackup/backup-my.cnf  --user=mysql
4. see that there are not triggers
mysql> show triggers;

Suggested fix:
here's patch which makes innobackup perl script to include .TRN and .TRG files:
http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/SOURCES/innobackup-trigger-tables.patch

This is fixed in upcoming 1.4.

This has bitten us pretty badly recently. Is there an official fix coming soon?

Pekka please release a new innobackup script.

Workaround (limited - for some): copy files manually

This bug has been fixed in Innobackup 1.4.0 which was released
on November 29, 2007. Innobackup 1.4.0 can be downloaded here:

http://www.innodb.com/download/innobackup-1.4.0