Upgrading a Geographic Edition Configuration

This section provides the following information to upgrade to a new Geographic Edition software version:

Upgrade Requirements and Software Support Guidelines
How to Prepare the Cluster for an Upgrade
How to Upgrade Geographic Edition Software
How to Verify Upgrade of Geographic Edition Software

To install a Geographic Edition software update (SRU), instead see Installing Software Updates.

Upgrade Requirements and Software Support Guidelines

Observe the following requirements and software-support guidelines on all clusters that have a partnership with the cluster that you are upgrading when you upgrade a cluster to the Geographic Edition 4.1 software:

Supported hardware - The cluster hardware must be a supported configuration for Geographic Edition 4.1 software. Contact your Oracle representative for information about Geographic Edition configurations that are currently supported.
Minimum Oracle Solaris OS version - The cluster must run on Oracle Solaris 11.1 software, including the most current required software updates.
Minimum Oracle Solaris Cluster version - The cluster must run on or be upgraded to either Oracle Solaris Cluster 4.0 or Oracle Solaris Cluster 4.1 software.

Note - All clusters in a partnership must run either Oracle Solaris Cluster 4.0 or Oracle Solaris Cluster 4.1 software. If a cluster is already running on Oracle Solaris Cluster 4.0 software, you are not required to upgrade it to Oracle Solaris Cluster 4.1 software to upgrade that cluster to Geographic Edition 4.1 software.
Cluster partnerships - For all clusters that have a partnership with the cluster that you are upgrading, all nodes of a cluster must run either Geographic Edition 4.0 or 4.1 software.

How to Prepare the Cluster for an Upgrade

Perform this procedure on all clusters that have a partnership with the cluster you are upgrading to remove the Geographic Edition layer from production. Perform all steps from the global zone only.

Before You Begin

Perform the following tasks:

Ensure that the configuration meets the requirements for the upgrade. See Upgrade Requirements and Software Support Guidelines.
Have available the installation media or the IPS publisher configured, documentation, and software updates for all software products that you are upgrading, including Oracle Solaris OS, Oracle Solaris Cluster software, and Geographic Edition 4.1 software.
Ensure that you have installed all the required software updates for your cluster configuration on each node of every cluster before you start upgrading the software. See Software Updates in Oracle Solaris Cluster 4.1 Release Notes for the location of software updates and installation instructions.

Ensure that the cluster is functioning properly.
1. From any node, view the current status of the cluster.
```
% cluster status
```
  See the cluster(1CL) man page for more information.
2. Search the /var/adm/messages log on the same node for unresolved error messages or warning messages.
3. Check the volume manager status.
Assume the root role on a node of the cluster.
Remove all application resource groups from protection groups.
Highly available applications do not have downtime during the Geographic Edition software upgrade.
```
# geopg remove-resource-group resourcegroup protectiongroup
```
See the geopg(1M) man page for more information.
Perform the preceding steps on all clusters that have a partnership with this cluster.
Stop all protection groups that are active on the cluster.
```
# geopg stop protectiongroup -e local
```
See the geopg(1M) man page for more information.
Stop the Geographic Edition infrastructure.
```
# geoadm stop
```
See the geoadm(1M) man page for more information.

Next Steps

Upgrade the Geographic Edition software on the clusters. Go to How to Upgrade Geographic Edition Software.

How to Upgrade Geographic Edition Software

Perform this procedure on all nodes of the cluster. You can perform this procedure on more than one node at the same time.

Caution - If the cluster is in a partnership, both partners must be installed with Geographic Edition 4.0 or 4.1 software before the Geographic Edition 4.1 software can start.

Before You Begin

Ensure that the cluster is prepared for upgrade. See How to Prepare the Cluster for an Upgrade.

Assume the root role on a node where you intend to upgrade Geographic Edition software.
Ensure that the cluster is functioning properly and that all nodes are online and part of the cluster.
1. From any node, view the current status of the cluster.
```
% cluster status
```
  See the cluster(1CL) man page for more information.
2. Search the /var/adm/messages log on the same node for unresolved error messages or warning messages.
3. Check the volume manager status.
Upgrade the Geographic Edition software to the new update or release.
```
# pkg update ha-cluster-geo-incorporation
```
Install all the required software updates as described in Installing Software Updates.
Ensure that Geographic Edition software upgrade is completed on all cluster nodes before you continue to the next step.
On one node of each partner cluster that you upgraded, enable Geographic Edition software.
```
# geoadm start
```
Update the public keys on all nodes on both partner clusters.
1. On each node in the local cluster, remove the public keys.
```
localnode# geops remove-trust -c remotecluster
```
2. On each node in the remote cluster, remove the public keys.
```
remotenode# geops remove-trust -c localcluster
```
3. On one node of the local cluster, import the public keys from the remote cluster.
```
localnode# geops add-trust -c remotecluster
```
4. On one node of the remote cluster, import the public keys from the local cluster.
```
remotenode# geops add-trust -c localcluster
```
5. On each node of each cluster, verify trust.
```
# geops verify-trust -c partnercluster
```
For a complete example of how to configure and join a partnership, see How to Join a Partnership in Oracle Solaris Cluster Geographic Edition System Administration Guide.
From one node in one of the partner clusters, add back to the protection group all application resource groups that you removed while you were preparing the cluster for upgrade.
```
# geopg add-resource-group resourcegroup protectiongroup
```
See the geopg(1M) man page for more information.
Start all the protection groups that you added.
```
# geopg start protectiongroup -e local [-n]
```
See the geopg(1M) man page for more information.

Next Steps

Go to How to Verify Upgrade of Geographic Edition Software.

How to Verify Upgrade of Geographic Edition Software

Perform this procedure to verify that the cluster is successfully upgraded to Geographic Edition 4.1 software. Perform all steps from the global zone only.

Before You Begin

Ensure that all upgrade procedures are completed for all cluster nodes that you are upgrading.

Assume the root role on each node.
On each upgraded node, view the installed levels of Geographic Edition software.
```
# geoadm -V
```
The last line of output states which version of Geographic Edition software the node is running. This version should match the version to which you just upgraded.

Note - The version number that the geoadm -v command returns does not coincide with the marketing release version numbers. The version number for Geographic Edition 4.1 software is 4.1.
Ensure that the cluster is running properly.
```
# geoadm status
```
(Optional) Perform a switchover to ensure that Geographic Edition software was installed properly.
```
# geopg switchover remotecluster protectiongroup
```
You must test your geographically separated cluster properly, so that no problems prevent a switchover. Upgrading the secondary cluster first and switching over to it enables you to verify that switchover still works. If the switchover fails, the primary site is untouched and you can switch back. If switchover works on the secondary site, then after a certain 'soak time' you can upgrade the primary site as well.

Note - A switchover might interrupt the services that are running on the cluster. You should carefully plan the required tasks and resources before you perform a switchover.
If you have added your application resource groups back into the protection groups, performing a switchover shuts down the applications on the original primary cluster and migrates the applications to the secondary cluster.

Skip Navigation Links
Exit Print View
	Oracle Solaris Cluster Geographic Edition Installation Guide Oracle Solaris Cluster 4.1