Sun Cluster Geographic Edition System Administration Guide

Appendix C Takeover Postconditions

This appendix provides details about the state of the primary and secondary clusters after you run the geopg takeover command.

This appendix contains the following sections:

Results of a Takeover When the Partner Cluster Can Be Reached

This section describes the activation state of the primary and secondary clusters before and after you run the geopg takeover command. The results described in this section assume that the partner cluster can be reached.

The following table describes the states of the clusters when you run the geopg takeover command on the secondary cluster, cluster-newyork.

Table C–1 Takeover Results of Running the geopg takeover Command on the Secondary Cluster

Cluster Role and State Before Takeover 

Cluster Role and State After Takeover 

cluster-paris: primary, deactivated

cluster-newyork: secondary, deactivated

cluster-paris: secondary, deactivated

cluster-newyork: primary, deactivated

 

cluster-paris: primary, activated

cluster-newyork: secondary, deactivated

cluster-paris: secondary, deactivated

cluster-newyork: primary, deactivated

cluster-paris: primary, deactivated

cluster-newyork: secondary, activated

cluster-paris: secondary, deactivated

cluster-newyork: primary, activated, with data replication stopped

cluster-paris: primary, activated

cluster-newyork: secondary, activated

cluster-paris: secondary, deactivated

cluster-newyork: primary, activated, with data replication stopped

The following table describes the states when you run the geopg takeover command on the primary cluster, cluster-paris.

Table C–2 Takeover Results of Running the geopg takeover Command on the Primary Cluster

Cluster Role and State Before Takeover 

Cluster Role and State After Takeover 

cluster-paris: primary, deactivated

cluster-newyork: secondary, deactivated

cluster-paris: primary, deactivated

cluster-newyork: secondary, deactivated

 

cluster-paris: primary, activated

cluster-newyork: secondary, deactivated

cluster-paris: primary, activated, with data replication stopped

cluster-newyork: secondary, deactivated

cluster-paris: primary, deactivated

cluster-newyork: secondary, activated

cluster-paris: primary, deactivated

cluster-newyork: secondary, deactivated

cluster-paris: primary, activated

cluster-newyork: secondary, activated

cluster-paris: primary, activated, with data replication stopped

cluster-newyork: secondary, deactivated

Results of a Takeover When the Partner Cluster Cannot Be Reached

This section describes the activation state of the primary and secondary clusters before and after you run a geopg takeover command when the partner cluster cannot be reached or when the protection group on the partner cluster is busy.

The following table describes the states when you run the geopg takeover command on the secondary cluster, cluster-newyork, and the primary cluster cannot be reached or the protection group on the primary cluster is busy.


Note –

The cluster role and state after the takeover, which is given in the table, is available only when the partner cluster can be reached again.


Table C–3 Takeover Results of Running the geopg takeover Command on the Secondary Cluster When the Primary Cluster Cannot Be Reached

Cluster Role and State Before Takeover 

Cluster Role and State After Takeover  

cluster-paris: primary, deactivated, synchronization status Unknown

cluster-newyork: secondary, deactivated, synchronization status Unknown

cluster-paris: primary, deactivated, synchronization status Error

cluster-newyork: primary, deactivated, synchronization status Error

 

cluster-paris: primary, activated, synchronization status Unknown

cluster-newyork: secondary, deactivated, synchronization status Unknown

cluster-paris: primary, activated, synchronization status Error

cluster-newyork: primary, deactivated, synchronization status Error

cluster-paris: primary, deactivated, synchronization status Unknown

cluster-newyork: secondary, activated, synchronization status Unknown

cluster-paris: primary, deactivated, synchronization status Error

cluster-newyork: primary, activated, with data replication stopped, synchronization status Error

cluster-paris: primary, activated, synchronization status Unknown

cluster-newyork: secondary, activated, synchronization status Unknown

cluster-paris: primary, activated, synchronization status Error

cluster-newyork: primary, activated, with data replication stopped, synchronization status Error

The following table describes the states when you run the geopg takeover command on the primary cluster, cluster-paris, and the secondary cluster cannot be reached or the protection group on the secondary cluster is busy.

Table C–4 Takeover Results of Running the geopg takeover Command on the Primary Cluster When the Secondary Cluster Cannot Be Reached

Cluster Role and State Before Takeover 

Cluster Role and State After Takeover 

cluster-paris: primary, deactivated, synchronization status Unknown

cluster-newyork: secondary, deactivated, synchronization status Unknown

cluster-paris: primary, deactivated, synchronization status OK, Error, or Mismatch

cluster-newyork: secondary, deactivated, synchronization status OK, Error, or Mismatch

 

cluster-paris: primary, activated, synchronization status Unknown

cluster-newyork: secondary, deactivated, synchronization status Unknown

cluster-paris: primary, activated, with data replication stopped, synchronization status OK, Error, or Mismatch

cluster-newyork: secondary, deactivated, synchronization status OK, Error, or Mismatch

cluster-paris: primary, deactivated, synchronization status Unknown

cluster-newyork: secondary, activated, synchronization status Unknown

cluster-paris: primary, deactivated, synchronization status OK, Error, or Mismatch

cluster-newyork: secondary, activated, synchronization status OK, Error, or Mismatch

cluster-paris: primary, activated, synchronization status Unknown

cluster-newyork: secondary, activated, synchronization status Unknown

cluster-paris: primary, activated, with data replication stopped, synchronization status OK, Error, or Mismatch

cluster-newyork: secondary, activated, synchronization status OK, Error, or Mismatch