Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Geographic Edition System Administration Guide |
1. Introduction to Administering the Geographic Edition Software
3. Administering the Geographic Edition Infrastructure
Geographic Edition Infrastructure Resource Groups
Disabling the Geographic Edition Software
How to Disable the Geographic Edition Software
Checking the Status of the Geographic Edition Infrastructure
Applying Patches to a Geographic Edition System
How to Prepare an Geographic Edition System for Patches
How to Install Patches on an Geographic Edition System
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
When you enable the Geographic Edition software, the cluster is ready to enter a partnership with another enabled cluster. You can use the CLI commands or the GUI to create a cluster partnership.
For more information about setting up and installing the Geographic Edition software, see the Oracle Solaris Cluster Geographic Edition Installation Guide.
This procedure enables the Geographic Edition infrastructure on the local cluster only. Repeat this procedure on all the clusters of your geographically separated cluster.
Before You Begin
Ensure that the following conditions are met:
The cluster is running the Solaris Operating System and the Oracle Solaris Cluster software.
The Oracle Solaris Cluster management-agent container for Oracle Solaris Cluster Manager is running.
The Geographic Edition software is installed.
The cluster has been configured for secure cluster communication by using security certificates, that is, nodes within the same cluster must share the same security certificates. This is done during Oracle Solaris Cluster installation.
When you upgrade to Oracle Solaris Cluster 3.3 5/11 software, the security certificates must be identical on all nodes of the cluster. Therefore, you must copy the security certificates manually from one node of the cluster to the other nodes of the cluster. For more information on copying the security files for the common agent container, see the procedures in How to Finish Upgrade to Oracle Solaris Cluster 3.3 5/11 Software in Oracle Solaris Cluster Upgrade Guide.
You must be assigned the Geo Operation RBAC rights profile to complete this procedure. For more information about RBAC, see Geographic Edition Software and RBAC.
# cluster list
If you must change the name of a cluster that is configured in a partnership, do not perform this step. Instead, follow instructions in Renaming a Cluster That Is in a Partnership.
Follow cluster naming guidelines as described in Planning Required IP Addresses and Hostnames in Oracle Solaris Cluster Geographic Edition Installation Guide. Cluster names must follow the same requirements as for host names.
# cluster rename -c newclustername oldclustername
For more information, see the cluster(1CL) man page.
Note - After you have enabled the Geographic Edition infrastructure, you must not change the cluster name while the infrastructure is enabled.
The local host file, hosts, is located in the /etc/inet directory.
# geoadm start
The geoadm start command enables the Geographic Edition infrastructure on the local cluster only. For more information, see the geoadm(1M) man page.
For a list of the Geographic Edition resource groups, see Geographic Edition Infrastructure Resource Groups.
# geoadm show # clresourcegroup status # clresource status
The output for the geoadm show command displays that the Geographic Edition infrastructure is active from a particular node in the cluster.
The output for the clresourcegroup status and clresource status commands displays that the geo-failovercontrol, geo-hbmonitor, and geo-clustername resources and the geo-infrastructure resource groups are online on one node of the cluster.
For more information, see the clresourcegroup(1CL) and clresource(1CL) man pages.
Example 3-1 Enabling the Geographic Edition Infrastructure in a Cluster
This example enables the Geographic Edition software on the cluster-paris cluster.
Start the Geographic Edition software on cluster-paris.
phys-paris-1# geoadm start
Ensure that the Geographic Edition infrastructure was successfully enabled.
phys-paris-1# geoadm show --- CLUSTER LEVEL INFORMATION --- Sun Cluster Geographic Edition is active on cluster-paris from node phys-paris-1 Command execution successful phys-paris-1#
Verify the status of the Geographic Edition resource groups and resources.
phys-paris-1# clresourcegroup status === Cluster Resource Groups === Group Name Node Name Suspended Status ---------- --------- --------- ------ geo-clusterstate phys-paris-1 No Online phys-paris-2 No Online geo-infrastructure phys-paris-1 No Online phys-paris-2 No Offline # clresource status === Cluster Resources === Resource Name Node Name State Status Message ------------- --------- ----- -------------- geo-clustername phys-paris-1 Online Online - LogicalHostname online. phys-paris-2 Offline Offline geo-hbmonitor phys-paris-1 Online Online - Daemon OK phys-paris-2 Offline Offline geo-failovercontrol phys-paris-1 Online Online - Service is online phys-paris-2 Offline Offline geo-servicetag phys-paris-1 Online_not_monitored Online_not_monitored phys-paris-1 Offline Offline
Next Steps
For information about creating protection groups, see the Oracle Solaris Cluster Geographic Edition Data Replication Guide that corresponds to the type of data replication software you are using.