You can load a mysqldump on the slave with a row based logging master as you would a
statement based logging master. Since row logs can be large you should consider a relay
log limit on the slave.
You can export ibd files if using xtradb engine with xtrabackup but other cases are
----- Original Message -----
From: Rick James [mailto:rjames@stripped]
Sent: Wednesday, October 27, 2010 03:00 PM
To: replication@stripped <replication@stripped>
Subject: rbr and reloaded slave (from mysqldump) ?
* 250GB table - PARTITIONed InnoDB; file_per_table
* RBR used
* Slave is hosed
* Sane ways of repairing the slave has been ruled out (it's a long story).
Plan A: Reload PARTITIONs by copying .ibd files. -- Rumor has it that
this will fail due to tablespace number (or something) being buried in
each .ibd. Such would make file copies of .ibd from a different machine
Question 1: Is this rumor true?
Plan B: We have a mysqldump and could reload. But, will RBR be
confused by the InnoDB blocks being slightly different after this load.
Question 2: What is the low level info in a RBR item? Does it include
a 'block number', which would probably be invalid after the reload? Or
does it contain something like the PK, which should be impervious?
Rick James - MySQL Geek
MySQL Replication Mailing List
For list archives: http://lists.mysql.com/replication
To unsubscribe: http://lists.mysql.com/replication?unsub=1
Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace.
Any dissemination, distribution or copying of the enclosed material is prohibited.
If you receive this transmission in error, please notify us immediately by e-mail
at abuse@stripped, and delete the original message.
Your cooperation is appreciated.