JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Geographic Edition Overview     Oracle Solaris Cluster 4.1
search filter icon
search icon

Document Information


1.  Introduction to Geographic Edition Software

2.  Key Concepts for Geographic Edition

Data Replication

Overview of Data Replication

Sun Availability Suite Feature

EMC Symmetrix Remote Data Facility Software

Oracle Data Guard Software

Sun ZFS Storage Appliance Software

Resource Groups and Device Groups

Overview of Resource Groups and Device Groups

Replication Resource Groups

Device Groups

Cluster Partnerships

Protection Groups

Overview of Protection Groups

Relationship Between Partnerships and Protection Groups

Protection Group Status

Application Resource Groups

Heartbeat Monitoring

Heartbeat Plug-ins

3.  Geographic Edition Architecture



Cluster Partnerships

A partnership establishes heartbeat monitoring between two clusters that are running Geographic Edition software. Clusters in a partnership exchange heartbeats to monitor each other's presence and health. You can configure a partnership between only two clusters, and only one partnership can be defined between the clusters.

If the partnership uses either application-based replication, such as Oracle Data Guard, or no replication, a member of the partnership can be either a global cluster or a zone cluster. Such a partnership can consist of two clusters of the same type or consist of one global cluster and one zone cluster.

If the partnership uses storage-based replication, only global clusters can be members of the partnership.

The two clusters must have an Internet connection with each other. A partnership establishes heartbeats between the clusters.

The Geographic Edition software uses the IP interconnect between partner clusters for management as well as heartbeats. For additional security when a public network is in use, use IPsec to secure the IP interconnect.

The Geographic Edition software enables you to specify a command to execute when a heartbeat-loss notification is issued. This command is executed with root permissions. You can also specify a list of email addresses to notify when a heartbeat-loss notification has been issued.

The following figure illustrates a partnership between two clusters.

Figure 2-1 Partnerships Between Clusters

image:Figure illustrates a partnership between two clusters

A single cluster can participate in more than one partnership with other clusters, but two clusters cannot be in more than one partnership with each other.