Mysteries of the Binary Log

Replication and Scale-Out
Location: Ballroom F Level: Intermediate
Average rating: ***..
(3.57, 7 ratings)

The purpose of the binary log is to record changes done to tables in the database. The binary log can then be used for replication, as well as for point-in-time recovery and in some limited cases also for auditing. If there are problems with replication, understanding the structure and how the server records changes to the binary log is necessary to resolve the problem.

There are many details about the binary log that have remained a mystery to most users. For example, what are the basic formats of the binary log and what are the pros and cons of each? If trouble arises, how can I find what went wrong in the binary log? How long should I keep a binary log? How does binary logging and backup work together? We answer all of these questions and more. Throughout the session, we will present the vital information you need to successfully employ the binary log. Some of the features discussed in this session include the following.

  • The structure of the binary log
  • Debugging using the binary log
  • How to perform point-in-time recovery
  • The role of the binary log in replication
  • Examining the binary log with mysqlbinlog
  • Using the binary log with backup
Photo of Chuck Bell

Chuck Bell


Dr. Charles A. Bell conducts research in emerging technologies and agile development techniques. He works for Sun Microsystems as a senior software engineer on the backup and replication team. He is currently one of the principle developers of the backup system. His contributions to the backup system include the new logging mechanism, the default drivers, and numerous minor enhancements. Working exclusively on the Windows platform, he is also the resident Windows expert for the team.

Photo of Lars Thalmann

Lars Thalmann


Dr. Lars Thalmann is the technical lead of replication and backup technology at MySQL. He has designed many of the features, and is leading the development of replication, online backup, character sets and XML. Dr. Thalmann has worked with clustering technology for many years and is one of the developers of NDB Cluster, the storage engine used in MySQL Cluster.

Photo of Mats Kindahl

Mats Kindahl


Mats Kindahl is senior software engineer in the MySQL replication team. He is the main architect and implementor of MySQL’s row-based replication, but has also developed the unit testing framework used by MySQL.

In the time before starting at MySQL, he has worked with research in formal methods, automated program analysis, distributed systems, and as implementor of C/C++ compilers.

Comments on this page are now closed.


Picture of Mark J. Levitt
Mark J. Levitt
04/14/2010 8:19am PDT

@C the slides are up now, see above (or this) link

Picture of C. Ed Felt
C. Ed Felt
04/14/2010 4:03am PDT

Great presentation. Can you please let me know when you post your slides?

  • Oracle
  • Monty Program
  • Calpont
  • Facebook
  • Gear6
  • Infobright, Inc
  • JasperSoft
  • Joyent
  • Kickfire
  • NorthScale, Inc.
  • Percona
  • Schooner Information Technology
  • Solid Quality Mentors (SolidQ)
  • Intel
  • Pentaho
  • Linux Pro Magazine

Sponsorship Opportunities

For information on exhibition and sponsorship opportunities at the conference, contact Yvonne Romaine at

Download the O'Reilly MySQL Conference & Expo Sponsor/ Exhibitor Prospectus

Media Partner Opportunities

Download the Media & Promotional Partner Brochure (PDF) for information on trade opportunities with O'Reilly conferences or contact mediapartners@

Press and Media

For media-related inquiries, contact Maureen Jennings at

O'Reilly MySQL Conference Newsletter

To stay abreast of conference news and to receive email notification when registration opens, please sign up for the O'Reilly MySQL Conference newsletter (login required).

Contact Us

View a complete list of O'Reilly MySQL Conference contacts.