Common Replication Administration Tasks empty server that you are provisioning with a backup of an existing database, both methods have the same result. If you are restoring a backup that overlaps the transactions that are already on the server, for example replacing a corrupted table with a partial dump from the source made using  mysqldump (which includes the GTIDs of all the transactions on the server, even though the dump is partial), use the first method of replacing the value of  gtid_purged . If you are restoring a backup that is disjoint from the transactions that are already on the server, for example provisioning a multi-source replica using dumps from two different servers, use the second method of adding to the value of  gtid_purged . gtid_set  must be a superset of the current value of  gtid_purged , and must not intersect with  gtid_subtract(gtid_executed,gtid_purged) . In other words, the new GTID set must  include any GTIDs that were already in  gtid_purged , and  must not  include any GTIDs in gtid_executed  that have not yet been purged.  gtid_set  also cannot include any GTIDs that are in @@global.gtid_owned , that is, the GTIDs for transactions that are currently being processed on the server. The result is that the global value of  gtid_purged  is set equal to  gtid_set , and the value of gtid_executed  becomes the union of  gtid_set  and the previous value of  gtid_executed . gtid_set must not  intersect with the current value of  gtid_executed . In other words, the new GTID set must not include any GTIDs in  gtid_executed , including transactions that are already also in  gtid_purged .  gtid_set  also cannot include any GTIDs that are in  @@global.gtid_owned , that is, the GTIDs for transactions that are currently being processed on the server. The result is that  gtid_set  is added to both  gtid_executed  and  gtid_purged . If any binary logs from MySQL 5.7.7 or older are present on the server (for example, following an upgrade of an older server to MySQL 8.0), after issuing a  SET @@GLOBAL.gtid_purged  statement, you might need to set binlog_gtid_simple_recovery=FALSE  in the server’s configuration file before restarting the server, otherwise  gtid_purged  can be computed incorrectly. See the description for  binlog_gtid_simple_recovery  for details of the situations in which this setting is needed. Once replication has been started it executes without requiring much regular administration. This section describes how to check the status of replication, how to pause a replica, and how to skip a failed transaction on a replica. To deploy multiple instances of MySQL, you can use InnoDB Cluster which enables you to easily administer a group of MySQL server instances in MySQL Shell. InnoDB Cluster wraps MySQL Group Replication in a programmatic environment that enables you easily deploy a cluster of MySQL instances to achieve high 17.1.7 Common Replication Administration Tasks Tip Note •To append your specified GTID set to  gtid_purged , use the following statement with a plus sign (+) before the GTID set: •To replace the value of  gtid_purged  with your specified GTID set, use the following statement: SET @@GLOBAL.gtid_purged = ’gtid_set’ SET @@GLOBAL.gtid_purged = ’+gtid_set’ 3577