Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Geographic Edition System Administration Guide |
1. Introduction to Administering the Geographic Edition Software
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 Modify Partnership Properties
Joining an Existing Partnership
How to Add a New Node to a Cluster in a Partnership
Renaming a Cluster That Is in a Partnership
How to Rename a Cluster That Is in a Partnership
Leaving or Deleting a Partnership
7. Administering Protection Groups
8. Monitoring and Validating the Geographic Edition Software
9. Customizing Switchover and Takeover Actions
A. Standard Geographic Edition Properties
B. Legal Names and Values of Geographic Edition Entities
C. Disaster Recovery Administration Example
E. Troubleshooting Geographic Edition Software
F. Deployment Example: Replicating Data With MySQL
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.
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. |
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.
# geops update partnershipname
Specifies the name of the partnership
Example 5-8 Resynchronizing a Partnership
This example resynchronizes a partnership.
# geops update paris-newyork-ps