Joining an Existing Partnership

When you define and configure a partnership, the partnership specifies a second cluster to be a member of that partnership. Then, you must configure this second cluster to join the partnership.

How to Join a Partnership

Perform this procedure from a node of the cluster that is joining the partnership.

Before You Begin

Ensure that the following conditions are met:

• The local cluster is enabled to run the Geographic Edition software.

• The partnership you want the cluster to join is defined and configured on another cluster (cluster-paris) and the local cluster (cluster-newyork) is specified as a member of this partnership.

• If a partner cluster is a zone cluster, either application-based replication such as Oracle Data Guard is configured or no data replication is used.

• Security has been configured on the clusters by installing the appropriate certificates.

  See Configuring Secure Cluster Communication Using Security Certificates for more information.

1. 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.

   ---

2. Confirm that the remote cluster that originally created the partnership, cluster-paris, can be reached at its logical hostname.

   # ping lh-paris-1

   For information about the logical hostname of the cluster, see How to Enable Geographic Edition Software.

3. Join the partnership.

   # geops join-partnership [-h heartbeatname] remoteclustername partnershipname

   -h heartbeatname

   Specifies a custom heartbeat to use in the partnership to monitor the availability of the partner cluster.

   If you omit this option, the default Geographic Edition heartbeat is used.

   Custom heartbeats are provided for special circumstances and require careful configuration. Consult your Sun specialist for assistance if your system requires the use of custom heartbeats. For more information about configuring custom heartbeats, see Chapter 6, Administering Heartbeats.

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

   You must configure the custom heartbeat that you provide in this option before you run the geops command.

   remoteclustername

   Specifies the name of a cluster that is currently a member of the partnership that is being joined. This cluster is used to retrieve the partnership configuration information.

   partnershipname

   Specifies the name of the partnership.

   For information about the names and values that are supported by Geographic Edition software, see Appendix B, Legal Names and Values of Geographic Edition Entities.

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

4. Verify that the cluster was added to the partnership and that the partnership properties were defined correctly.

   # geops list
   # geoadm status

Example 5-3 Joining a Partnership

This example joins the cluster-newyork cluster in the partnership that was created on cluster-paris in Example 5-1.

# geops join-partnership cluster-paris paris-newyork-ps
# geops list
# geoadm status

Example 5-4 Creating and Joining a Partnership With a Remote Cluster in a Different Domain

This example creates and configures the paris-newyork-ps partnership between clusters cluster-paris.france and cluster-newyork.usa.

1. On one node of cluster-paris.france, configure trust for the partnership.

   phys-paris-1# geops add-trust -c cluster-newyork.usa

2. On one node of cluster-newyork.usa, configure trust for the partnership.

   phys-newyork-1# geops add-trust -c cluster-paris.france

3. On each node of both clusters, verify that trust has been set up properly, both between the local cluster and partner cluster and among nodes of the local cluster.

   phys-newyork-1# geops verify-trust -c cluster-paris.france
   phys-newyork-2# geops verify-trust -c cluster-paris.france
   phys-newyork-1# geops verify-trust
   phys-newyork-2# geops verify-trust
   phys-paris-1# geops verify-trust -c cluster-newyork.usa
   phys-paris-2# geops verify-trust -c cluster-newyork.usa
   phys-paris-1# geops verify-trust
   phys-paris-2# geops verify-trust

4. On cluster-paris.france, create the partnership paris-newyork-ps.

   cluster-paris# geops create -c cluster-newyork.usa -p Description=Transatlantic \
   -p Notification_emailaddrs=sysadmin@companyX.com paris-newyork-ps

5. On cluster-newyork.usa, join the partnership paris-newyork-ps.

   cluster-newyork# geops join-partnership cluster-paris.france paris-newyork-ps

6. Verify that the partnership has been created successfully.

   # geops list
   # geoadm status