MySQL Group Replication enables you to create elastic, highly-available, fault-tolerant replication topologies. MySQL Group Replication provides distributed state machine replication with strong coordination between servers. Servers coordinate themselves automatically when they are part of the same group. Groups can operate in a single-primary mode with automatic primary election, where only one server accepts database updates at a time. With Commvault, you can back up groups, where single-primary mode option is enabled.
Commvault MySQL Group Replication backup is built to utilize the secondary servers for backup operations. This enables you to offload backup activity from a primary server to secondary servers. If the MySQL Group Replication is found to be broken at any point of time, the backup from such offline servers is not useful as it will not include the latest data.
In such events, backups can be run on a different secondary server/primary server. This ensures a continuous backup activity.
The following are the capabilities of the Commvault MySQL Group Replication backups:
-
Offloading the backup operations on primary server for improved performance.
-
Flexibility to utilize the primary server for seamless backup activity in the event of all secondary server failures.
Terminology
This documentation uses the following terminology:
|
Term |
Definition |
|---|---|
|
Primary server |
The primary node in MySQL group replication. This node might change in MySQL group replication. |
|
Secondary server |
The secondary nodes in MySQL group replication. These nodes might change in MySQL group replication. |
|
Primary Commvault instance |
The MySQL instance that has cluster settings configured in the Instance Property of MySQL Instance dialog box. You can manage backups and restores from the primary Commvault instance. |
|
Secondary Commvault instance |
All other MySQL instances, except the primary Commvault instance, that are configured for MySQL cluster backups. |