Go to main content

Oracle® Solaris Cluster Data Replication Guide for MySQL

Exit Print View

Updated: August 2018
 
 

Validating a MySQL Protection Group

When the configuration status of a protection group is displayed as Error in the geoadm status output, you can validate the configuration by using the geopg validatecommand. This command checks the current status of the protection group and its entities.

If the protection group and its entities are valid, then the configuration status of the protection groups is set to OK. If the geopg validatecommand finds an error in the configuration files, then the command displays an error message, and the configuration remains in the Error state. In such a case, you can fix the error in the configuration, and rerun the geopg validatecommand.

This section provides the following information:

Data Replication Layer Process for Validating the Application Resource Groups and Data Replication Entities

During protection group validation, the MySQL data replication layer validates the application resource groups and the data replication entities by verifying that an application resource group in the protection group has its Auto_start_on_new_cluster property set to false.

When you bring a protection group online on the primary cluster, bring the application resources groups participating in that protection group online only on the same primary cluster. Setting the Auto_start_on_new_cluster property to false prevents the Oracle Solaris Cluster resource group manager from automatically starting the application resource groups. In this case, the startup of resource groups is reserved for the disaster recovery framework.

Application resource groups should be online only on the primary cluster when the protection group is activated.

The MySQL geocontrol module supplies a script that is used by the script-based plug-in module. The script entry points require the same set of arguments. These arguments are validated for semantics and completeness. The following validation checks are performed:

  • Are all of the mandatory arguments defined?

  • Is the configured MySQL database resource defined?

  • Is the specified replication resource configured with a correct start command, if the resource exists already?

  • Are the long and short ping intervals numeric?

When the validation is complete, the disaster recovery framework creates and brings online the replication resource group and its resources if they don't already exist. If a resource group or resource of the same name already exists, the disaster recovery framework might modify its properties. The framework cannot create a new resource group or a resource of the same name if one already exists. After creating the necessary resources, the framework adds the application resource group to the protection group.

How to Validate a MySQL Protection Group

The geopg validate command validates the configuration of the protection group on the local cluster only. To validate the protection group configuration on the partner cluster, rerun the command on the partner cluster.


Note -  You can also accomplish this procedure by using the Oracle Solaris Cluster Manager GUI. Click Partnerships, click the partnership name, highlight the protection group name, and click Validate. For more information about Oracle Solaris Cluster Manager, see Chapter 12, Using the Oracle Solaris Cluster Manager Browser Interface in Administering an Oracle Solaris Cluster 4.4 Configuration.

Before You Begin

Ensure that the following conditions are met:

  • The protection group you want to validate exists locally.

  • The common agent container is online on all nodes of both clusters in the partnership.

  • Validate the configuration of the protection group on the local cluster only.
    # geopg validate protection-group
    protection-group

    The unique name of a single protection group.

Example 1  Validating the Configuration of a Protection Group

In the following example, the configuration of a protection group is validated:

# geopg validate mysql-pg