Using MySQL Enterprise Backup with Group Replication 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 configuration file  mysqld-auto.cnf , if it is found in the corrupted server’s data directory, by copying it to a safe location outside of the data directory. This is for preserving the server’s Section 5.1.9.3, “Persisted System Variables” , which are needed later. c. Delete all contents in the data directory of  s3 . For example: d. Restore the backup of  s2  onto the host of  s3 . With this approach, we are rebuilding  s3  as a new member, for which we do not need or do not want to use the old binary and relay logs in the backup; therefore, if these logs have been included in your backup, exclude them using the  -- skip-binlog  and  --skip-relaylog  options: 3. Restore the  mysqld-auto.cnf  file for s3 (only required if s3 used persistent system variables).  The settings for the Section 5.1.9.3, “Persisted System Variables”  that were used to configure the failed member must be provided to the restored server. These settings are to be found in the  mysqld- auto.cnf  file of the failed server, which you should have preserved in step 2 above. Restore the file to the data directory of the restored server. See Restoring Persisted System Variables on what to do if you do not have a copy of the file. 4. Start the restored server.  For example, on Linux distributions that use systemd: Note Do NOT restore the corrupted server’s  auto.cnf  file to the data directory of the new member—when the rebuilt  s3  joins the group as a new member, it is going to be assigned a new server UUID. 3762 If the system variables  innodb_data_home_dir ,  innodb_log_group_home_dir , and innodb_undo_directory  point to any directories other than the data directory, they should also be made empty; otherwise, the restore operation fails. Note If you have healthy binary log and relay logs in the backup that you can transfer onto the target host with no issues, you are recommended to follow the easier procedure as described in Restoring a Failed Member above. s3>  mysqlbackup --defaults-file=/etc/my.cnf \ --datadir=/var/lib/mysql \ --backup-image=/backups/my.mbi_2206_1429 \ --backup-dir=/tmp/restore_‘date +%d%m_%H%M‘ \ --skip-binlog --skip-relaylog \ copy-back-and-apply-log s3> rm -rf /var/lib/mysql/* s3> systemctl stop mysqld s2/backups>  scp my.mbi_2206_1429 s3:/backups systemctl start mysqld