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
Geographic Edition Infrastructure Resource Groups
Enabling the Geographic Edition Software
How to Enable Geographic Edition Software
Disabling the Geographic Edition Software
How to Disable the Geographic Edition Software
Checking the Status of the Geographic Edition Infrastructure
Applying Software Updates to a Geographic Edition System
Guidelines When Applying Software Updates to a Geographic Edition System
How to Prepare a Geographic Edition System for Software Updates
How to Install Software Updates on a 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
This section contains the following information:
Guidelines When Applying Software Updates to a Geographic Edition System
How to Prepare a Geographic Edition System for Software Updates
How to Install Software Updates on a Geographic Edition System
Observe the following guidelines and requirements to update Geographic Edition software:
You must run the same software updates for Oracle Solaris Cluster software and the common agent container software on all nodes of the same cluster.
Within a cluster, the software updates for each node on which you have installed Geographic Edition software must meet the Oracle Solaris Cluster software update requirements.
All nodes in the same cluster must have the same version of Geographic Edition software and the same software updates. However, primary and secondary clusters can run different versions of Geographic Edition software, provided that each version of Geographic Edition is correctly updated and the versions are no more than one release different.
To ensure that the updates have been installed properly, install the software updates on your secondary cluster before you install the software updates on the primary cluster.
For additional information about Geographic Edition software updates, see the software update README file.
See the Oracle Solaris Cluster 4.1 Release Notes for a list of any required software updates.
To view the current status of the cluster, run the following command from any node:
% cluster status
See the cluster(1CL) man page for more information.
Search the /var/adm/messages log on the same node for unresolved error messages or warning messages.
This step ensures that resource groups are not stopped when you later stop the protection groups.
# geopg remove-resource-group resourcegroup protectiongroup
See the geopg(1M) man page for more information.
# geopg stop -e local protectiongroup
See the geopg(1M) man page for more information.
# geoadm stop
Shutting down the infrastructure ensures that a software update installation on one cluster does not affect the other cluster in the partnership.
See the geoadm(1M) man page for more information.
# /usr/sbin/cacaoadm stop
Next Steps
Install the required software updates for the Geographic Edition software. Go to How to Install Software Updates on a Geographic Edition System.
Perform this procedure on all nodes of the cluster.
Update the secondary cluster before you update the primary cluster, to permit testing.
Before You Begin
Perform the following tasks:
Ensure that the Oracle Solaris OS is installed to support Geographic Edition software.
If Oracle Solaris software is already installed on the node, you must ensure that the Oracle Solaris installation meets the requirements for Geographic Edition software and any other software that you intend to install on the cluster.
Ensure that Geographic Edition software packages are installed on the node.
Ensure that you completed all steps in How to Prepare a Geographic Edition System for Software Updates.
To view the current status of the cluster, run the following command from any node:
% cluster status
See the cluster(1CL) man page for more information.
Search the /var/adm/messages log on the same node for unresolved error messages or warning messages.
If you are updating Oracle Solaris Cluster software, perform updates on both clusters.
For instructions on performing a software update, see Chapter 11, Updating Your Software, in Oracle Solaris Cluster System Administration Guide
# /usr/sbin/cacaoadm start
# geoadm start
# geopg add-resource-group resourcegroup protectiongroup
See the geopg(1M) man page for more information.
# geopg start -e local [-n] protectiongroup
See the geopg(1M) man page for more information.
Next Steps
After you update the secondary cluster, perform a sanity test on the Geographic Edition software, and then repeat this procedure on the primary cluster.