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

Introduction to 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.  Deployment Example: Replicating Data With MySQL

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

Index

Leaving or Deleting a Partnership

You can also use the geops command to remove a cluster from a partnership and release all the resources that are associated with the partnership.

Because this command destroys the local partnership configuration information, when the last member leaves a partnership, the partnership no longer exists.

How to Leave a Partnership

Before You Begin

Ensure that the following conditions are met:

  1. Log in to a cluster node.

    You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Geographic Edition Software and RBAC.

  2. Verify that the partnership does not have any protection groups.
    # geopg list

    If you find that the partnership contains protection groups, you can delete them with the geopg delete command. For information about deleting protection groups, see one of the following data replication guides:

  3. Remove the partnership on a node of the cluster that is a member of the partnership.
    # geops leave-partnership partnershipname
    partnershipname

    Specifies the name of the partnership


    Note - The geops leave-partnership command deletes the heartbeats configured for the partnership, including custom heartbeats.


    For more information, refer to the geops(1M) man page.

Example 5-6 Leaving a Partnership

In this example, the cluster-paris cluster leaves the paris-newyork-ps partnership.

phys-paris-1# geops leave-partnership paris-newyork-ps

Example 5-7 Deleting a Partnership

After the cluster-paris cluster leaves the paris-newyork-ps partnership, as described in the previous example, the only remaining member of the partnership is the cluster-newyork cluster. You can delete the paris-newyork-ps partnership by forcing the cluster-newyork cluster to leave the partnership.

phys-newyork-1# geops leave-partnership paris-newyork-ps

Next Steps

Repeat this procedure on the other cluster in the partnership.