Bug #8780 InnoDB: Last MySQL binlog file position
Submitted: 24 Feb 2005 16:52 Modified: 24 Feb 2005 17:05
Reporter: Keith Larson Email Updates:
Status: Not a Bug Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S2 (Serious)
Version:mysql Ver 12.22 Distrib 4.0.23 OS:for pc-linux (i686) FedoraC2
Assigned to: CPU Architecture:Any

[24 Feb 2005 16:52] Keith Larson
Based on the Documentation here:

1. Take the backup, use ibbackup --apply-log to restore it, and put the restored backup and the log files to the right places for the new slave.
2. Edit the my.cnf file of the new slave so that you put skip-slave-start to the [mysqld] section.
3. Start the new slave mysqld (version >= 3.23.48 or >= 4.0.2). It prints the latest MySQL binlog position the backup knows of.

I should be able to see the 
InnoDB: Last MySQL binlog file position 0 128760128, file name ./hundin-bin.006

How do I see this or where does it put it ? 

I started mysql with /etc/rc.d/init.d/mysql start 

How to repeat:
I started mysql with /etc/rc.d/init.d/mysql start 

Suggested fix:
Update Doc with more information.
[24 Feb 2005 17:05] Heikki Tuuri

mysqld prints its output to the .err file.


ibbackup --apply-log

prints the last known binlog position.

You can order Hot Backup support from http://www.innodb.com/order.php and MySQL/InnoDB support from http://www.mysql.com/network/