This video will show you step by step how to set up master slave replication using global transaction identifiers (GTID).
The global transaction ID introduces a new event attached to each event group in the binlog. (An event group is a collection of events that are always applied as a whole.
The replica remembers the global transaction ID of the last event group applied from the old primary server. This makes it easy to know where to resume replication on the new primary server because global transaction IDs are known throughout the replication hierarchy. This does not apply to old style replication; in this case, the replica only knows the specific filename and offset of the old primary server of the last applied event. There is no easy way to guess from this the correct filename and offset on the new primary server.
0:00 Start
1:20 Setting up replication
6:19 Check
7:29 The end
#mariadb #mariadb-dump #replication