Actions Performed by the Sun Cluster Geographic Edition Software During a Takeover

When you run the geopg takeover command, the software confirms that the volume sets are in a Replicating or Logging state on the secondary cluster.

If the original primary cluster, cluster-paris, can be reached, the software performs the following actions:

• Removes affinities and resource dependencies between all the application resource groups in the protection group and the internal resource group if the protection group was active

• Takes the application resource groups offline and places them in an Unmanaged state

• Unmounts the primary volumes that correspond to the device groups in the protection group

• Stops data replication by placing all volume sets in logging mode

• Reverses the role of all volume sets

On the original secondary cluster, cluster-newyork, the software performs the following actions:

• Places all volume sets into logging mode

• Reverses the role of all volume sets

• Runs the script that is specified in the RoleChange_ActionCmd property

• If the protection group was active on the original secondary cluster before the takeover, brings all application resource groups online and adds affinities and resource dependencies between the application resource group and the internal resource group

If the command completes successfully, the secondary cluster, cluster-newyork, becomes the new primary cluster for the protection group. Volume sets associated with a device group in the protection group have their role reversed according to the role of the protection group on the local cluster. If the protection group was active on the original secondary cluster before the takeover, the application resource groups are brought online on the new primary cluster. If the original primary cluster can be reached, it becomes the new secondary cluster of the protection group. Replication of all volume sets that are associated with the device groups of the protection group is stopped.

After a successful takeover, data replication is stopped. If you want to continue to suspend replication, specify the -n option when you use the geopg start command. This option prevents the start of data replication from the new primary cluster to the new secondary cluster.

This command returns an error if any of the previous operations fails. Use the geoadm status command to view the status of each component. For example, the Configuration status of the protection group might be set to Error, depending on the cause of the failure. The protection group might be activated or deactivated.

If the Configuration status of the protection group is set to Error, revalidate the protection group by using the procedures described in How to Validate a Sun StorageTek Availability Suite Protection Group.

If the configuration of the protection group is not the same on each partner cluster, you need to resynchronize the configuration by using the procedures described in How to Resynchronize a Sun StorageTek Availability Suite Protection Group.