Practical configuration.
WHAT TO PREPARE
A unique server identifier on each Binary logging on the primary A replication account with the minimum privilege
WHAT THE STEPS ARE
Configure and restart the primary Take a consistent backup, noting the log position Restore it on the replica Point the replica at the primary and the position Start replication Verify
WHY THE POSITION MATTERS
It tells the replica where to begin applying changes.
WHAT MODERN SETUPS USE INSTEAD
Globally unique transaction identifiers, removing manual position tracking.
WHY THAT IS PREFERABLE
It makes failover and reconfiguration far simpler.
HOW TO CHECK STATUS
The replica status command.
WHAT TO LOOK AT
Whether both threads are running The lag figure Any error
WHAT A STOPPED THREAD MEANS
An error occurred applying a change.
WHAT TO DO
Read the error, fix the cause, and resume.
WHAT TO NEVER DO
Skip errors routinely to make replication run.
WHY
The replica silently diverges, and the divergence is discovered during a failover.
HOW TO VERIFY CONSISTENCY
A checksum comparison across tables.
WHAT TO RUN PERIODICALLY
That comparison.
