Upgrading Failover Zones

A failover zone is a non-global zone that is configured with the HA for Oracle Solaris Zones data service so that it can be managed by the Oracle Solaris Cluster software. If you have failover zones of brand type solaris configured on the cluster, perform this procedure in conjunction with the procedures for the cluster upgrade method that you use.

How to Upgrade a Failover Zone

Note - This task is not needed for solaris10 brand failover zones.

Determine the nodes where the resource group that manages the failover zone of brand type solaris is offline.
```
# clresourcegroup status resourcegroup
```
Suspend the resource group that manages the failover zone of brand type solaris.
```
# clresourcegroup suspend resourcegroup
```
Perform the standard or rolling upgrade on the nodes where the resource group that manages the failover zones is offline.
Perform all steps, including booting into the new boot environment, in How to Upgrade the Software (Standard Upgrade) or How to Upgrade the Software (Rolling Upgrade). Then return to this procedure.
Perform the standard or rolling upgrade on the nodes where the resource group that manages the failover zones of brand type solaris is online.
Perform Step 1 through Step 5 in How to Upgrade the Software (Standard Upgrade) or Step 1 through Step 5 in How to Upgrade the Software (Rolling Upgrade). Do not perform the final step in those procedures to boot the machine into the new boot environment. Instead, return to this procedure after you complete this task.
Synchronize the universally unique IDs (UUID) of the updated boot environments.
1. Determine the UUID of the updated boot-environment root dataset of the node where the resource group that manages the failover zone of brand type solaris is online.
  You will see output similar to the following:
```
phys-schost-1# beadm list -H
...
b175b-SC;8fe53702-16c3-eb21-ed85-d19af92c6bbd;R;/;756
...
```
  In this example, the UUID is 8fe53702-16c3-eb21-ed85-d19af92c6bbd and the updated boot environment is b175b-SC.
2. Set the same UUID on the updated boot environment for the other nodes where the resource group that manages the failover zone of brand type solaris is offline.
```
phys-schost-2# zfs set org.opensolaris.libbe:uuid=uuid rpool/ROOT/BE
```
  For example:
```
phys-schost-2# zfs set org.opensolaris.libbe:uuid=8fe53702-16c3-eb21-ed85-d19af92c6bbd rpool/ROOT/b175b-SC
```
3. If a cluster node that was upgraded in Step 3 contains other kinds of solaris brand zones that are configured and running, update the UUID.
  Perform this step on each node where a resource group that manages a solaris brand failover zone is offline. On the solaris brand zone's updated boot environment, set the same UUID that you identified in Step a.
```
phys-schost-2# zfs set org.opensolaris.libbe:parentbe=uuid poolname/zonepath/rpool/ROOT/bename
```
  For example:
```
phys-schost-2# zoneadm list -cv
…
   1 myzone1       running    /zones/myzone1   solaris  shared
…

phys-schost-2# zlogin myzone1 beadm list -H
solaris;4391e8aa-b8d2-6da9-a5aa-d8b3e6ed6d9b;NR;/;606941184;static;1342165571

phys-schost-2# zfs set org.opensolaris.libbe:parentbe=8fe53702-16c3-eb21-ed85-d19af92c6bbd \
rpool/zones/myzone1/rpool/ROOT/solaris
```
Resume the resource group that manages the failover zone of brand type solaris.
```
# clresourcegroup resume resourcegroup
```
Switch the resource group that manages the failover zone of brand type solaris to a node that was already booted into the updated boot environment and verify that the zone started correctly.
```
# clresourcegroup switch -n phys-schost-2 resourcegroup
```
Boot the node from Step 4, where the resource group that manages the failover zone of brand type solaris had initially been online, into its updated boot environment.

Next Steps

Go to Chapter 5, Completing the Upgrade.

Skip Navigation Links
Exit Print View
	Oracle Solaris Cluster Upgrade Guide Oracle Solaris Cluster 4.1