Concepts·MySQL
MySQL Binary Log
Every change is written to the binary log before it reaches you. That log is what makes both replication and point-in-time recovery possible - and it is on by default in MySQL 8, whether or not you planned for it.
Backup and Restore Guide 24 of 45 Intermediate
- OSUbuntu 26.04 LTS
- MySQL8.4.10-0ubuntu0.26.04.1
- BinlogROW format, enabled by default
- TimeAbout 14 min
Binary logging is enabled by default from 8.0. On 5.7 it was off unless configured, which is why older documentation treats it as an opt-in.
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| db-a01 | 192.168.0.81 | Ubuntu 26.04 LTS | Primary / Source / Replica Set Member 1 | 2 Core | 4 GB | 50 GB |
This guide includes
Use this when you need point-in-time recovery or replication. This matters because every change is written to the binary log before it ever reaches you - and those files grow forever unless something removes them.
- confirming it is on, and reading the three values that decide everything downstream
- finding the numbered series of files, and where the server is currently writing
- managing retention before the disk does it for you
Before you start
- MySQL 8 on db-a01.
-
Confirm it is on and read its shape
-
See the files and where the server is writing
-
Manage retention before the disk does it for you