Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Geographic Edition System Administration Guide

Search Scope:

- This Document
- Entire Library

## Resynchronizing a Partnership

Partner clusters that become disconnected during a disaster situation might force the administrator to perform a takeover for a protection group that the partners share. When both clusters are brought online again, both partner clusters might report as the primary of the protection group. You must resynchronize the configuration information of the local protection group with the configuration information that is retrieved from the partner cluster.

If a cluster that is a member of a partnership fails, when the cluster restarts, it detects whether the partnership parameters have been modified while it was down. You decide which partnership configuration information you want to keep: the information on the cluster that failed or the information on the failover cluster. Then, resynchronize the configuration of the partnership accordingly.

You do not need to resynchronize the configuration information in the following situations if the original secondary cluster goes down and resumes operation later.

Use the `geoadm status` command to check whether you need to resynchronize a partnership. If the `Configuration` status is `Synchronization Status Error`, you need to synchronize the partnership. If the `Local status` is `Partnership Error`, do not resynchronize the partnership. Instead, wait until a heartbeat exchange occurs.

## How to Resynchronize a Partnership

Perform this procedure from a node on the cluster that needs to be synchronized with the information retrieved from the partner cluster.

Before You Begin

Ensure that the following conditions are met:

- The local cluster is Geographic Edition enabled.

- The local cluster was an active member of the partnership before failing.

| Caution - Resynchronizing a partnership overwrites the partnership configuration on the cluster where the command is run with the information from the partner cluster.

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. Resynchronize the partnership.

       # geops update partnershipname

   partnershipname

     Specifies the name of the partnership

Example 5-8 Resynchronizing a Partnership

This example resynchronizes a partnership.

    # geops update paris-newyork-ps

Copyright © 2004, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |