In some Geographic Edition configurations, a zone cluster can be configured as a cluster partner. Observe the following guidelines for the use of zone clusters in a cluster partnership.
Public-network IP addresses - A zone cluster that is configured in a Geographic Edition configuration must meet the following public-network requirements:
Each zone-cluster node must have a public-network IP address that corresponds to the zone-cluster node's hostname.
The zone-cluster node's public-network IP address must be accessible by all nodes in the Geographic Edition configuration's partner cluster.
Each zone-cluster node must have a failover IP address that maps to the hostname that corresponds to the zone-cluster name.
Data replication requirements – Zone clusters can be cluster partners in a Geographic Edition configuration that meets either of the following conditions:
Application-based data replication is used. Geographic Edition supports Oracle Data Guard, MySQL, and Geographic Edition script-based plug-ins application-based data replication.
No data replication is used.
Mixed cluster types – The partnership can use other zone clusters or a combination of zone clusters and global clusters.
Framework packages –nGeographic Edition framework packages are required in the global zones in all cases, even if Geographic Edition is only going to be enabled in the zone clusters. The Geographic Edition framework package is ha-cluster/geo/geo-framework.
Storage-based replication – If storage-based replication is used, with the exception of Oracle ZFS Storage Appliance replication, all members of a cluster partnership must be global clusters. Zone clusters can exist in a global-cluster partnership that uses storage-based replication, but the zone clusters themselves cannot be members of a partnership that uses storage-based replication.
If Oracle ZFS Storage Appliance replication is used, members of a cluster partnership can be global clusters, zone clusters, or a combination of the two.
Starting the infrastructure – You can start the Geographic Edition infrastructure from within a zone cluster node, but not from within any other type of non-global zone.
GUI – The Oracle Solaris Cluster Manager GUI cannot be used to manage Geographic Edition components of a zone cluster that is a partnership member.