MySQL Forums
Forum List  »  Backup

MySQL Enterprise Backup with MySQL InnoDB Cluster Best Practice
Posted by: Jason Miele
Date: July 14, 2017 07:10AM

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?

Options: ReplyQuote


Subject
Views
Written By
Posted
MySQL Enterprise Backup with MySQL InnoDB Cluster Best Practice
634
July 14, 2017 07:10AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.