Go to main content

Administering the Disaster Recovery Framework for Oracle® Solaris Cluster 4.4

Exit Print View

Updated: June 2019

Tuning the Heartbeat Properties

Default heartbeats are created as part of partnership creation. If you use a custom heartbeat, the custom heartbeat should be created before you create a partnership. You can modify the properties of the default and custom heartbeats by using the geohb set-prop command. For more information about this command, refer to the geohb(8) man page.

Note -  Custom heartbeats are provided for special circumstances and require careful configuration. Consult your Oracle specialist for assistance if your system requires the use of custom heartbeats.

If you modify the default value of the Query_interval property, ensure that the interval is sufficiently long. An interval that is too short causes a timeout and heartbeat-loss event before the logical hostname resource is available. This failover should result in no more than two unanswered heartbeat requests. Setting a default Query_interval value of 120 seconds with the default heartbeat.retries parameter of 3 enables the peer cluster to be unresponsive for 6 minutes (120 * 3 ) without having a false failure declared.

The heartbeat.retries parameter is specified in the com.sun.cluster.agent.geocontrol.xml file.

If you adjust the delay setting of the Query_interval property, ensure that the following condition is met:

Query_interval > worst-case-logical-host-failover-time / 2

You must empirically determine the logical-host failover time for the cluster in question.

The following must be true to avoid false failures:

Query_interval > worst-case-logical-host-failover-time / 3

You should not change the heartbeat.retries value. If you want to change the default value of the heartbeat.retries property, contact an Oracle service representative.

How to Modify the Heartbeat Properties

Note -  You can also accomplish this procedure by using the Oracle Solaris Cluster Manager browser interface. Click Partnerships, click the partnership name to go to its page, click the heartbeat name to go to its page, click the Properties tab, and click Edit to access the listed properties for editing. For Oracle Solaris Cluster Manager log-in instructions, see How to Access Oracle Solaris Cluster Manager in Administering an Oracle Solaris Cluster 4.4 Configuration.
  1. Log in to a cluster node.

    You must be assigned the Geo Management rights profile to complete this procedure. For more information, see Disaster Recovery Framework Rights Profiles in Installing and Configuring the Disaster Recovery Framework for Oracle Solaris Cluster 4.4.

  2. Modify the heartbeat properties.
    # geohb set-prop -p property-setting [-p…] heartbeat-name
    –p property-setting

    Specifies the default properties of the heartbeat.

    A heartbeat property is assigned a value by a name=statement pair. Multiple properties can be set at one time by using multiple statements.

    For more information about the properties you can set, see Standard Disaster Recovery Framework Properties.


    Specifies an identifier for the heartbeat settings.

    For information about the names and values that are supported by the disaster recovery framework, see Legal Names and Values of Disaster Recovery Framework Entities.

    For more information about the geohb command, refer to the geohb(8) man page.

Example 15  Modifying the Properties of the Default Heartbeat

This example modifies the settings for the default heartbeat between cluster-paris and cluster-newyork.

# geohb set-prop -p Query_interval=60 hb_cluster-paris~cluster-newyork