When running three MySQL 5.7.18 Enterprise servers in a MySQL InnoDB Cluster, the MySQL documentation states the best practice is to run the MySQL Enterprise Backup 4.1.0 on a secondary server in the cluster (to avoid a performance impact on the primary). However, when we run the backup on a secondary server, we receive the error: cannot run backup because super-read-only is set to 'on'. So, our backup script now sets super-read-only to 'off' on the secondary server, then runs the backup, then sets super-read-only to 'on'.
As our goal is to run a hot backup in order to maintain high-availability and fault-tolerance. When our secondary MySQL server temporarily sets super-read-only to false, will it affect a failover from primary to itself in the event the primary fails during a backup?
As our goal is to run a hot backup in order to maintain high-availability and fault-tolerance. When our secondary MySQL server temporarily sets super-read-only to false, will it affect a failover from primary to itself in the event the primary fails during a backup?