Description:
This feature request is related to this forum thread:
https://forums.mysql.com/read.php?28,658830,658830#msg-658830
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'.
Our goal is to run a hot backup on secondary to maintain primary performance and monitor the backup’s status in the MySQL Enterprise Monitor portal. We appear to have two options:
1. Take a standard enterprise backup from the current primary
2. Take a enterprise backup from a current secondary using the --no-history-logging option so that mysqlbackup doesn't try and execute DDL and DML for the history tables (https://dev.mysql.com/doc/mysql-enterprise-backup/4.1/en/backup-metadata-options.html#opti...)
If we take option one, then we impact the performance of primary. Yet option two prevents the history from showing up in MySQL Enterprise Monitor Portal. Perhaps we need a new setting in the MySQL Database: super-read-only-except-for-backups
The new setting would permit the MySQL Enterprise backup to write the status into a MySQL Server operating as secondary, which will display in the MySQL Enterprise Portal.
How to repeat:
1) Take a enterprise backup from a current secondary operating in an InnoDB Cluster
© 2025, Oracle Corporation and/or its affiliates