Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Geographic Edition System Administration Guide Oracle Solaris Cluster 4.1 |
1. Introduction to Administering the Geographic Edition Software
3. Administering the Geographic Edition Infrastructure
4. Administering Access and Security
5. Administering Cluster Partnerships
7. Administering Protection Groups
8. Monitoring and Validating the Geographic Edition Software
9. Customizing Switchover and Takeover Actions
A. Standard Geographic Edition Properties
B. Legal Names and Values of Geographic Edition Entities
C. Disaster Recovery Administration Example
E. Troubleshooting Geographic Edition Software
F. Deployment Example: Replicating Data With MySQL
MySQL Replication Resource Group
MySQL Application Resource Group
Initial Configuration of MySQL Replication
Installing MySQL and Configuring the MySQL Database Resource Group
How to Configure the MySQL Replication
Configuring the MySQL Application Resource Group
Administering MySQL Protection Groups
Planning for Your MySQL Protection Group
Creating, Modifying, Validating, and Deleting a MySQL Protection Group
How to Create the MySQL Configuration
Modifying a MySQL Protection Group
Validating a MySQL Protection Group
Administering MySQL Application Resource Groups
How to Add an Application Resource Group to a MySQL Protection Group
How to Delete an Application Resource Group From a MySQL Protection Group
Administering MySQL Data-Replicated Components
How to Add a Data-Replicated Component to a MySQL Protection Group
Data Replication Subsystem Process for Verifying the Replicated Component
How to Modify a MySQL Data-Replicated Component
How to Delete a Data-Replicated Component From a MySQL Protection Group
Replicating a MySQL Protection Group Configuration to a Partner Cluster
Activating and Deactivating a MySQL Protection Group
Activating a MySQL Protection Group
Deactivating a MySQL Protection Group
Resynchronizing a MySQL Protection Group
Recovery Strategy After a Takeover of a MySQL Protection Group
How to Recover After a Takeover
To delete a protection group on all clusters, run the geopg delete command on each cluster where the protection group exists.
Before You Begin
Before deleting a protection group, ensure that the following conditions are met:
The protection group exists locally.
The protection group is offline on the local cluster.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information, see Geographic Edition Software and RBAC.
Note - To keep the application resource groups online while deleting a protection group, you must remove the application resource groups from the protection group.
The cluster-nyc cluster is the primary cluster. For a sample cluster configuration, see Example Geographic Edition Cluster Configuration.
The following command deletes the configuration of the protection group from the local cluster. The command also removes the replication resource group for each device group in the protection group.
# geopg delete protection-group
In this syntax, protection-group specifies the name of the protection group.
If the deletion is unsuccessful, the configuration status is set to Error. Fix the cause of the error, and rerun the geopg delete command.
Example F-2 Deleting a Protection Group
In the following example, a protection group is deleted from both partner clusters:
# rlogin cluster-nyc -l root cluster-nyc# geopg delete mysql-pg # rlogin cluster-sfo -l root cluster-sfo# geopg delete mysql-pg
Example F-3 Deleting a Protection Group While Keeping Application Resource Groups Online
In the following example, two application resource groups (apprg1 and apprg2) are kept online while the protection group that they share, mysql-pg, is deleted. First, the application resource groups are removed from the protection group. Then, the protection group is deleted.
# geopg remove-resource-group apprg1,apprg2 mysql-pg # geopg stop -e global mysql-pg # geopg delete mysql-pg