Go to main content

Oracle® Solaris Cluster Geographic Edition Data Replication Guide for ZFS Snapshots

Exit Print View

Updated: February 2017
 
 

Migrating Services That use ZFS Snapshot Replication with a Takeover

This section describes how to perform a protection group takeover in order to migrate services to a partner cluster. You perform a takeover when applications need to be brought online on the existing secondary partner cluster regardless of whether the data is completely synchronized between the primary and secondary ZFS datasets. The applications will be started on the existing secondary partner as a result of the takeover if the protection group has been activated on that partner.

How to Perform a Takeover for a Oracle Solaris ZFS Snapshot Protection Group

Use the standard protection group takeover procedure to perform takeover of a ZFS snapshot replication protection group to migrate services to the existing secondary partner. For more information, see Forcing a Takeover of a Protection Group in Oracle Solaris Cluster 4.3 Geographic Edition System Administration Guide.

Before You Begin

Ensure that the following conditions are met before you attempt a takeover:

  • Geographic Edition infrastructure is up and running on the secondary cluster.

  • Protection group is configured on the secondary cluster, and its Configuration status is OK

This procedure uses the example names paris for the current primary cluster and newyork for the current secondary cluster. The goal is to takeover the protection group to make newyork the new primary.

  1. Type the following command in one node of newyork to do the takeover to newyork.
    # geopg takeover [-f] protection-group
  2. After the takeover is complete, check that the protection group is now primary on newyork.
    # geopg status protection-group
  3. If the Geographic Edition infrastructure is up and running on the original primary paris and the Geographic Edition infrastructure on newyork can reach paris, on paris check that it is secondary now and that the protection group is deactivated.
    #geoadm status protection-group
  4. Check that the replication status resources associated with the protection group are offline.

    Data replication is deactivated on a takeover.

    # clresourcegroup status -v replication-status-rg-for-pg
    # clresource status -v replication-status-rs
  5. If the protection group is in activated state on the new primary newyork, then check that the application resource group and its resources are online.

    Otherwise, activate the protection group on newyork to bring the application online. Type the following commands to check the status of the application:

    # clresourcegroup status application-rg-in-pg
    # clresource status -g application-rg-in-pg