A MySQL database resource group can belong to only one protection group.
The MySQL geographic replication was developed with the disaster recovery framework script-based plug-in module, so it must comply with all rules of the script-based plug-in. For each protection group, you must provide a script-based plug-in configuration file on each node. In addition, the MySQL geographic replication brings in its own configuration file, which is needed only at registration.
The MySQL geographic replication creation is an automated process that takes the MySQL geographic configuration file as input and performs the necessary actions. The essential content of this file consists of key=value pairs. The keys are:
Application resource group, which is unmanaged and contains at least the logical host for client access.
Absolute path for the script-based plug-in configuration file.
Description for the protection group.
Timeout for the extensive ping test. The default is 60 seconds if this variable is unset. This timeout is used at check_takeover where it must be verified as the remote site is unavailable.
Name of the protection group to create.
Name of the partnership.
Switch for setting the read-only variable on the MySQL slave. If the read-only variable should not be set, leave this value undefined. Any entry here triggers the read-only variable to be set.
Resource group names that contain the MySQL database resource on the clusters. If the resource group names on the clusters differ, provide a comma-separated list.
Name of the partnership.
Resource names configured as the master and slave MySQL database resources. If the resource names on the clusters differ, provide a comma-separated list.
Name of the replicated component to create in this protection group.
Name of the replication resource group.
Name of the replication resource.
Timeout for the short ping test. The default is 10 seconds if this variable is unset. The short ping timeout is used whenever a connection should succeed but is not required to succeed.