Go to main content

Administering the Disaster Recovery Framework for Oracle® Solaris Cluster 4.4

Exit Print View

Updated: June 2019

Resynchronizing a Partnership

This section provides information about resynchronizing partnership information between its partner clusters.

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 or Oracle Solaris Cluster Manager 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 to resynchronize partnership configuration information.

Note -  You can also accomplish this procedure by using the Oracle Solaris Cluster Manager browser interface. Click Partnerships, highlight the name of the partnership, and click Update Partnership. For Oracle Solaris Cluster Manager log-in instructions, see How to Access Oracle Solaris Cluster Manager in Administering an Oracle Solaris Cluster 4.4 Configuration.

Before You Begin

Ensure that the following conditions are met:

  • The local cluster is disaster recovery framework 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. Log in to a node on the cluster that needs to be synchronized with the information retrieved from the partner cluster.

    You must be assigned the Geo Management rights profile to complete this procedure. For more information, see Disaster Recovery Framework Rights Profiles in Installing and Configuring the Disaster Recovery Framework for Oracle Solaris Cluster 4.4.

  2. Resynchronize the partnership.
    # geops update partnership-name

    Specifies the name of the partnership

Example 8  Resynchronizing a Partnership

This example resynchronizes a partnership.

# geops update paris-newyork-ps