JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Geographic Edition Data Replication Guide for Hitachi TrueCopy and Universal Replicator
search filter icon
search icon

Document Information

Preface

1.  Replicating Data With Hitachi TrueCopy and Universal Replicator Software

2.  Administering Hitachi TrueCopy and Universal Replicator Protection Groups

3.  Migrating Services That Use Hitachi TrueCopy and Universal Replicator Data Replication

Detecting Cluster Failure on a System That Uses Hitachi TrueCopy or Universal Replicator Data Replication

Detecting Primary Cluster Failure

Detecting Secondary Cluster Failure

Migrating Services That Use Hitachi TrueCopy or Universal Replicator Data Replication With a Switchover

Validations That Occur Before a Switchover

Results of a Switchover From a Replication Perspective

How to Switch Over a Hitachi TrueCopy or Universal Replicator Protection Group From Primary to Secondary

Forcing a Takeover on a System That Uses Hitachi TrueCopy or Universal Replicator Data Replication

Validations That Occur Before a Takeover

Results of a Takeover From a Replication Perspective

How to Force Immediate Takeover of Hitachi TrueCopy or Universal Replicator Services by a Secondary Cluster

Recovering Services to a Cluster on a System That Uses Hitachi TrueCopy or Universal Replicator Replication

How to Resynchronize and Revalidate the Protection Group Configuration

How to Perform a Failback-Switchover on a System That Uses Hitachi TrueCopy or Universal Replicator Replication

How to Perform a Failback-Takeover on a System That Uses Hitachi TrueCopy or Universal Replicator Replication

Recovering From a Switchover Failure on a System That Uses Hitachi TrueCopy or Universal Replicator Replication

Switchover Failure Conditions

Recovering From Switchover Failure

How to Make the Original Primary Cluster Primary for a Hitachi TrueCopy or Universal Replicator Protection Group

How to Make the Original Secondary Cluster Primary for a Hitachi TrueCopy or Universal Replicator Protection Group

Recovering From a Hitachi TrueCopy or Universal Replicator Data Replication Error

How to Detect Data Replication Errors

How to Recover From a Hitachi TrueCopy or Universal Replicator Data Replication Error

A.  Geographic Edition Properties for Hitachi TrueCopy and Universal Replicator

Index

Migrating Services That Use Hitachi TrueCopy or Universal Replicator Data Replication With a Switchover

Perform a switchover of a Hitachi TrueCopy or Universal Replicator protection group when you want to migrate services to the partner cluster in an orderly fashion. A switchover consists of the following:

This section provides the following information:

Validations That Occur Before a Switchover

When a switchover is initiated by using the geopg switchover command, the data replication subsystem runs several validations on both clusters. The switchover is performed only if the validation step succeeds on both clusters.

First, the replication subsystem checks that the Hitachi TrueCopy or Universal Replicator device group is in a valid aggregate device group state. Then, it checks that the local device group states on the target primary cluster, cluster-newyork, are 23, 33, 43, or 53. The local device group state is returned by the pairvolchk -g device-group-name -ss command. These values correspond to a PVOL_PAIR or SVOL_PAIR state. The Hitachi TrueCopy or Universal Replicator commands that are run on the new primary cluster, cluster-newyork, are described in the following table.

Table 3-1 Hitachi TrueCopy and Universal Replicator Switchover Validations on the New Primary Cluster

Aggregate Device Group State
Valid Device Group State on Local Cluster
Hitachi TrueCopy or Universal Replicator Switchover Commands That Are Run on cluster-newyork
SMPL
None
None
Regular primary
23, 43
No command is run, because the Hitachi TrueCopy or Universal Replicator device group is already in the PVOL_PAIR state.
Regular secondary
33, 53
horctakeover -g dg [-t]

The-t option is specified when the fence_level of the Hitachi TrueCopy or Universal Replicator device group is async. The value is calculated as 80% of the Timeout property of the protection group. For example, if the protection group has a Timeout of 200 seconds, the value of -t used in this command is 80% of 200 seconds, or 160 seconds.

Takeover primary
None
None
Takeover secondary
None
None

Results of a Switchover From a Replication Perspective

After a successful switchover, at the data replication level the roles of the primary and secondary volumes have been switched. The PVOL_PAIR volumes that were in place before the switchover become the SVOL_PAIR volumes. The SVOL_PAIR volumes in place before the switchover become the PVOL_PAIR volumes. Data replication will continue from the new PVOL_PAIR volumes to the new SVOL_PAIR volumes.

The Local-role property of the protection group is also switched regardless of whether the application could be brought online on the new primary cluster as part of the switchover operation. On the cluster on which the protection group had a Local role of Secondary, the Local-role property of the protection group becomes Primary. On the cluster on which the protection group had a Local-role of Primary, the Local-role property of the protection group becomes Secondary.

How to Switch Over a Hitachi TrueCopy or Universal Replicator Protection Group From Primary to Secondary

Before You Begin

For a successful switchover, data replication must be active between the primary and the secondary clusters and data volumes on the two clusters must be synchronized.

Before you switch over a protection group from the primary cluster to the secondary cluster, ensure that the following conditions are met:


Caution

Caution - If you have configured the Cluster_dgs property, only applications that belong to the protection group can write to the device groups specified in the Cluster_dgs property.


  1. Log in to a cluster node.

    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 in Oracle Solaris Cluster Geographic Edition System Administration Guide.

  2. Initiate the switchover.

    The application resource groups that are a part of the protection group are stopped and started during the switchover.

    # geopg switchover [-f] -m newprimarycluster protectiongroupname
    -f

    Forces the command to perform the operation without asking you for confirmation

    -m newprimarycluster

    Specifies the name of the cluster that is to be the new primary cluster for the protection group

    protectiongroupname

    Specifies the name of the protection group

Example 3-1 Forcing a Switchover From Primary to Secondary

This example performs a switchover to the secondary cluster.

# geopg switchover -f -m cluster-newyork tcpg