Using MySQL Enterprise Backup with Group Replication This does not prevent  mysqlbackup  from finishing the backup though. You can avoid the warning by using the  --no-history-logging  option with your backup command. This is not an issue for MySQL Enterprise Backup 8.0.21 and higher—see Using MySQL Enterprise Backup with Group Replication for details. Assume one of the members ( s3  in the following example) is irreconcilably corrupted. The most recent backup of group member  s2  can be used to restore  s3 . Here are the steps for performing the restore: Notes Restoring a Failed Member • For MySQL Enterprise Backup 8.0.18 and earlier,  If the system variable sql_require_primary_key  is set to  ON  for the group, MySQL Enterprise Backup is not able to log the backup progress on the servers. This is because the backup_progress  table on the server is a CSV table, for which primary keys are not supported. In that case,  mysqlbackup  issues the following warnings during the backup operation: 1. Copy the backup of s2 onto the host for s3.  The exact way to copy the backup depends on the operating system and tools available to you. In this example, we assume the hosts are both Linux servers and use SCP to copy the files between them: 2. Restore the backup.  Connect to the target host (the host for  s3  in this case), and restore the backup using MySQL Enterprise Backup. Here are the steps: a. Stop the corrupted server, if it is still running. For example, on Linux distributions that use systemd: b. Preserve the two configuration files in the corrupted server’s data directory,  auto.cnf  and mysqld-auto.cnf  (if it exists), by copying them to a safe location outside of the data directory. This is for preserving the server’s UUID and Section 5.1.9.3, “Persisted System Variables”  (if used), which are needed in the steps below. s2/backups>  scp my.mbi_2206_1429 s3:/backups s3> systemctl stop mysqld 181011 11:17:06 MAIN WARNING: MySQL query ’CREATE TABLE IF NOT EXISTS mysql.backup_progress( ‘backup_id‘ BIGINT NOT NULL, ‘tool_name‘ VARCHAR(4096) NOT NULL, ‘error_code‘ INT NOT NULL, ‘error_message‘ VARCHAR(4096) NOT NULL, ‘current_time‘ TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,‘current_state‘ VARCHAR(200) NOT NULL ) ENGINE=CSV DEFAULT CHARSET=utf8 COLLATE=utf8_bin’: 3750, Unable to create a table without PK, when system variable ’sql_require_primary_key’ is set. Add a PK to the table or unset this variable to avoid this message. Note that tables without PK can cause performance problems in row-based replication, so please consult your DBA before changing this setting. 181011 11:17:06 MAIN WARNING: This backup operation’s progress info cannot be logged. 181113 21:31:08 MAIN WARNING: This backup operation cannot write to backup progress. The MySQL server is running with the --super-read-only option. • For MySQL Enterprise Backup 8.0.20 and earlier , when backing up a secondary member, as MySQL Enterprise Backup cannot write backup status and metadata to a read-only server instance, it might issue warnings similar to the following one during the backup operation: 3759