JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Geographic Edition System Administration Guide     Oracle Solaris Cluster 4.0
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

Configuring Trust Between Partner Clusters

How to Configure Trust Between Two Clusters

How to Remove Trust Between Two Clusters

Creating and Modifying a Partnership

How to Create a Partnership

How to Modify Partnership Properties

Joining an Existing Partnership

How to Join a Partnership

Adding a New Cluster Node

How to Add a New Node to a Cluster in a Partnership

Renaming a Cluster Node

Renaming a Cluster That Is in a Partnership

How to Rename a Cluster That Is in a Partnership

Leaving or Deleting a Partnership

How to Leave a Partnership

Resynchronizing a Partnership

How to Resynchronize a Partnership

6.  Administering Heartbeats

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.  Error Return Codes for Script-Based Plug-Ins

Index

Adding a New Cluster Node

When you add a new node to a cluster that is in a partnership, you must perform additional tasks on that node to make it an active participant in the Geographic Edition configuration.

How to Add a New Node to a Cluster in a Partnership

Perform all steps from the new node.

  1. Add the new node to the cluster.

    Follow procedures in Chapter 8, Adding and Removing a Node, in Oracle Solaris Cluster System Administration Guide.

  2. Install Geographic Edition, data replication, and application software on the new node.
  3. If the cluster with the new node is the primary for any activated protection groups, remove application resource groups from those protection groups.

    This step is necessary to avoid application downtime.

    # geopg remove-resource-group resourcegroup protectiongroup
  4. Deactivate all protection groups that are active on this cluster locally.
    # geopg stop -e local protectiongroup
  5. Stop the Geographic Edition infrastructure.
    # geoadm stop
  6. Re-enable the Geographic Edition infrastructure.

    This action recreates each Geographic Edition resource group and adds all nodes in the cluster, including the new node, to the node list.

    # geoadm start
  7. Reactivate the protection groups that you deactivated in Step 4.
    # geopg start -e local protectiongroup
  8. Restore any application resource groups that you removed in Step 3.
    # geopg add-resource-group resourcegroup protectiongroup