Solaris Cluster How to Migrate a Failover Non-Global Zone (NGZ) to a Non Clustered System
(Doc ID 1997071.1)
Last updated on AUGUST 14, 2020
Applies to:Solaris Cluster - Version 3.2 to 3.3 U2 [Release 3.2 to 3.3]
Oracle Solaris on SPARC (64-bit)
To show by example the migration of a Failover Zone to a non-cluster node.
This example shows a 5.10 Global Zone (GZ) and 5.10 Non-Global Zone (NGZ).
There is a brief update at the bottom of this document: 5.11.x/4.x note.
Zones can be used in different ways in an OSC environment.
They can be configured as non-voting nodes (members of a Resource Group (RG)), failover zones (containers),
zone clusters or just a regular zones. Only failover zones should have a zonepath based on 'shared' storage
and thus be subject to OSC fencing (keys and reservations). Either way, whether a Sparse Root or Whole Root
zone, used in or by cluster or not, the zones will have OSC CORE and very likely AGENT pkg's installed in them.
I present you with the scenario of having a whole-root failover zone (zone2) which I will migrate to a node
which is not running OSC (Node3).
First, information on the RG and Resources that manage this Failover Zone:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!