Oracle® Solaris Cluster Geographic Edition Data Replication Guide for Oracle Solaris Availability Suite

Exit Print View

Updated: July 2014, E39670-01
 
 

Forcing a Takeover on Systems That Use Availability Suite

You perform a takeover when applications need to be brought online on the secondary cluster regardless of whether the data is completely consistent between the primary volume and the secondary volume. The information in this section assumes that the protection group has been started.

The following steps occur after a takeover is initiated:

  • If the former primary cluster, cluster-paris, can be reached and the protection group is not locked for notification handling or some other reason, the protection group is deactivated.

    For a reminder of which cluster is cluster-paris, see Example Geographic Edition Cluster Configuration in Oracle Solaris Cluster Geographic Edition System Administration Guide .

  • Data volumes of the former primary cluster, cluster-paris, are taken over by the new primary cluster, cluster-newyork.


    Note -  This data might not be consistent with the original primary volumes. Data replication from the new primary cluster, cluster-newyork, to the former primary cluster, cluster-paris, is stopped.
  • The protection group is activated without data replication.

For details about the possible conditions of the primary and secondary cluster before and after takeover, see Appendix D, Takeover Postconditions, in Oracle Solaris Cluster Geographic Edition System Administration Guide .