Documentation Home
MySQL Enterprise Backup 9.2 User's Guide
Related Documentation Download this Manual
PDF (US Ltr) - 1.3Mb
PDF (A4) - 1.3Mb


MySQL Enterprise Backup 9.2 User's Guide  / Using MySQL Enterprise Backup  /  Using MySQL Enterprise Backup with Group Replication

Chapter 9 Using MySQL Enterprise Backup with Group Replication

For how to use MySQL Enterprise Backup to back up and subsequently restore aGroup Replication member, seeUsing MySQL Enterprise Backup with Group Replication.

When working with aGroup Replication setup,mysqlbackup makes the backup information available to all members of the server group by making sure that thebackup_history,backup_sbt_history (whenusing the SBT API), andbackup_progress tables are updated on a primary node for eachmysqlbackup operation. For the feature to work on any host in a Group Replication setup, make sure the following requirements are met:

  • Host names or host addresses contained in themember_host column in theperformance_schema.replication_group_members table must be resolvable bymysqlbackup.

  • In addition to themysqlbackup@localhost account created on each host as described inSection 4.1.2, “Grant MySQL Privileges to Backup Administrator”, accounts for the usermysqlbackup to accessall hosts in the group have been created onevery member of the server group. These are sample statements for creating the accounts:

    CREATE USER 'mysqlbackup'@'host1' IDENTIFIED BY 'password';CREATE USER 'mysqlbackup'@'host2' IDENTIFIED BY 'password';CREATE USER 'mysqlbackup'@'host3' IDENTIFIED BY 'password';...

    Or, if the host names fall into a pattern, use a wildcard for the host names (if allowed by your environment's security policy) to perform the same task with a single statement; for example:

    CREATE USER 'mysqlbackup'@'host_' IDENTIFIED BY 'password';
  • The accountmysqlbackup@localhostAND all other accounts for accessing the hosts (i.e.,mysqlbackup@host1,mysqlbackup@host2,mysqlbackup@host3, etc, or simplymysqlbackup@host_ in our example) usethe same password for server access. This is needed because, depending on how host names are resolved,mysqlbackup will likely be using two accounts to finish a backup job on a Group Replication set up (one for the actual backup operation, the other for updating the history and progress tables on a primary host), but only one password can be specified in the backup command. Therefore, the accounts must use the same password.

  • All the privileges granted tomysqlbackup@localhost as described inSection 4.1.2, “Grant MySQL Privileges to Backup Administrator” are also granted to all other accounts with whichmysqlbackup connects to the hosts:

    GRANT SELECT ON performance_schema.replication_group_members TO 'mysqlbackup'@'host1'; GRANT SELECT ON performance_schema.replication_group_members TO 'mysqlbackup'@'host2'; GRANT SELECT ON performance_schema.replication_group_members TO 'mysqlbackup'@'host3';[More grant statements for other privileges for all hosts ...]

    Or, if the host names fall into a pattern, use a wildcard for the host names (if allowed by your environment's security policy) to perform the same task; for example:

    GRANT SELECT ON performance_schema.replication_group_members TO 'mysqlbackup'@'host_'; [More grant statements for other privileges...]