Using MySQL Enterprise Backup with Group Replication s3> rm -rf /var/lib/mysql/* 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. 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‘ copy-back-and-apply-log The command above assumes that the binary logs and relay logs on  s2 and  s3  have the same base name and are at the same location on the two servers. If these conditions are not met, you should use the  --log-bin  and --relay-log  options to restore the binary log and relay log to their original file paths on  s3 . For example, if you know that on  s3  the binary log’s base name is  s3-bin  and the relay-log’s base name is  s3-relay-bin , your restore command should look like: Being able to restore the binary log and relay log to the right file paths makes the restore process easier; if that is impossible for some reason, see Rebuild the Failed Member to Rejoin as a New Member. If you cannot supply the failed member’s original  server_uuid  to the restored member by restoring its old  auto.cnf  file, you must let the restored member join the group as a new member; see instructions in Rebuild the Failed Member to Rejoin as a New Member below on how to do that. c. Delete all contents in the data directory of  s3 . For example: d. Restore backup of  s2  onto the host for  s3 : Note mysqlbackup --defaults-file=/etc/my.cnf \ --datadir=/var/lib/mysql \ --backup-image=/backups/my.mbi_2206_1429 \ --log-bin=s3-bin --relay-log=s3-relay-bin \ --backup-dir=/tmp/restore_‘date +%d%m_%H%M‘ copy-back-and-apply-log 3. Restore the  auto.cnf  file for s3.  To rejoin the replication group, the restored member  must  have the same  server_uuid  it used to join the group before. Supply the old server UUID by copying the auto.cnf  file preserved in step 2 above into the data directory of the restored member. Note 4. 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 member. 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. 3760