We have a PSE05 "Master" and PSE06 "Slave" (PRODUCTION servers) both are
We have a third slave PSE07 which is Ubuntu 64-bit. This is our 'live
backup' so to speak. We take mysqld down daily on there and tarball the
/var/lib/mysql and /var/log/mysql as snapshots (since mysqldump would take
a week literally to re-import).
Our data is about 100GB and nearly 1 Billion records and growing by several
hundred thousand per day.
We had some replication hose-up where someone accidentally wrote to the
PSE06 slave. This wasn't caught right away and so it cascaded and queued up
about 130 rows to be written. Obviously going through this whole business:
mysql> stop slave; SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1; start slave; show
Would take WAY too long and painful. So we thought we'd shut down PSE06,
scp the .tgz file from PSE07, dump it in, set the pointers on the slave and
let replication catch up.
Not so much.
So is this even possible. Are the ibdata files binary compatible between
"bit" versions (or even different OS's for that matter)
We are getting errors:
101013 23:56:22 [Warning] Neither --relay-log nor --relay-log-index were
used; so replication may break when this MySQL server acts as a slave and
has his hostname changed!! Please use '--relay-log=mysqld-relay-bin' to
avoid this problem.^M
root@pse06:~# find /home/mysql/ | grep relay
Oct 13 23:55:27 pse06 mysqld: 101013 23:55:27 [Warning] Neither
--relay-log nor --relay-log-index were used; so replication may break when
this MySQL server acts as a slave and has his hostname changed!! Please use
'--relay-log=mysqld-relay-bin' to avoid this problem.
Oct 13 23:55:27 pse06 mysqld: 101013 23:55:27 [ERROR] Failed to open
the relay log '/home/mysql/binlog/mysqld-relay-bin.005693' (relay_log_pos
Oct 13 23:55:27 pse06 mysqld: 101013 23:55:27 [ERROR] Could not find
target log during relay log initialization