binary log
A file containing a record of all statements that attempt to change table data. These statements can be replayed to bring slave servers up to date in a replication scenario, or to bring a database up to date after restoring table data from a backup. The binary logging feature can be turned on and off, although Oracle recommends always enabling it if you use replication or perform backups.
You can examine the contents of the binary log, or replay those statements during replication or recovery, by using the mysqlbinlog command. For full information about the binary log, see , "The Binary Log". For MariaDB configuration options related to the binary log, see , "Binary Log Options and Variables".
For the MySQL Enterprise Backup product, the file name of the binary log and the current position within the file are important details. To record this information for the master server when taking a backup in a replication context, you can specify the --slave-info option.
Prior to MariaDB 5.0, a similar capability was available, known as the update log. In MariaDB 5.0 and higher, the binary log replaces the update log.
See also binlog.
See also MySQL Enterprise Backup.
See also replication.