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

Document Information

Preface

1.  Introduction to Administering the Geographic Edition Software

2.  Before You Begin

3.  Administering the Geographic Edition Infrastructure

4.  Administering Access and Security

5.  Administering Cluster Partnerships

6.  Administering Heartbeats

Introduction to Heartbeats

Creating a Heartbeat

How to Create a Heartbeat

Creating a Heartbeat Plug-in

How to Create Heartbeat Plug-in

Modifying a Heartbeat Plug-in Property

How to Modify the Properties of a Heartbeat Plug-in

Deleting Heartbeats and Heartbeat Plug-ins

How to Delete a Heartbeat

How to Delete a Plug-in From a Heartbeat

Displaying Heartbeat Configuration Information

How to Display Heartbeat Configuration Information

Tuning the Heartbeat Properties

How to Modify the Heartbeat Properties

Creating a Heartbeat That Uses a Custom Heartbeat Plug-in

Creating a Custom Heartbeat Plug-in

How to Add a Custom Heartbeat Plug-in to an Existing Default Heartbeat

How to Create a Custom Heartbeat Plug-in and Add It to a Custom Heartbeat

Configuring Heartbeat-Loss Notification

Configuring the Heartbeat-Loss Notification Properties

Creating an Action Shell Script for Heartbeat-Loss

7.  Administering Protection Groups

8.  Monitoring and Validating the Geographic Edition Software

9.  Customizing Switchover and Takeover Actions

10.  Script-Based Plug-Ins

A.  Standard Geographic Edition Properties

B.  Legal Names and Values of Geographic Edition Entities

C.  Disaster Recovery Administration Example

D.  Takeover Postconditions

E.  Troubleshooting Geographic Edition Software

F.  Deployment Example: Replicating Data With MySQL

G.  Error Return Codes for Script-Based Plug-Ins

Index

Creating a Heartbeat

This section describes procedures for creating heartbeats.

How to Create a Heartbeat

Use this procedure to create a new heartbeat. To use the heartbeat with a partnership, you must create the heartbeat before you create a partnership. If you create a partnership before you create the custom heartbeat, the default heartbeat that is used by the partnership will prevent the custom heartbeat from being created.

If you create a custom heartbeat, you must add at least one plug-in to prevent the partnership from remaining in degraded mode.

A custom heartbeat prevents the default heartbeat from being used during partnership creation. If you want to use the default heartbeat for your partnership, you must delete the custom heartbeat before running the geops create command.

  1. Log in to a cluster node.
  2. Become superuser or assume a role that is assigned the Geo Management RBAC rights profile.

    For more information about RBAC, see Geographic Edition Software and RBAC.


    Note - If you use a role with Geo Management RBAC rights, ensure that the /var/cluster/geo ACLs are correct on each node of both partner clusters. If necessary, become superuser on the cluster node and set the correct ACLs.

    # chmod A+user:username:rwx:allow /var/cluster/geo

    The /var/cluster/geo directory must have the correct access control lists (ACL) applied for compatibility between the Geo Management RBAC rights profile and Oracle Data Guard.


  3. Create the heartbeat.
    # geohb create -r remoteclustername \
    [-p propertysetting [-p…]] heartbeatname
    -r remoteclustername

    Specifies the name of the remote, secondary partner cluster.

    -p propertysetting

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

    For more information about the properties you can set, see Appendix A, Standard Geographic Edition Properties.

    heartbeatname

    Specifies an identifier for the heartbeat.

    If you create a custom heartbeat, you must add at least one plug-in to prevent the partnership from remaining in degraded mode.


    Caution

    Caution - The name of the custom heartbeat on each cluster in the same partnership must be different. Choose a name that identifies the heartbeat uniquely, such as paris-to-newyork on the cluster cluster-paris and newyork-to-paris on cluster cluster-newyork.


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

Example 6-1 Creating a Heartbeat

This example creates a heartbeat that is named paris-to-newyork.

# geohb create -r cluster-newyork paris-to-newyork