Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Geographic Edition Data Replication Guide for Hitachi TrueCopy and Universal Replicator

Search Scope:

- This Document
- Entire Library

## Activating a Hitachi TrueCopy or Universal Replicator Protection Group

When you activate a protection group, the protection group assumes the role that you assigned to it during configuration. For more information about configuring protection groups, see How to Create and Configure a Hitachi TrueCopy or Universal Replicator Protection Group That Does Not Use Oracle Real Application Clusters.

You can activate a protection group in the following ways:

- Globally – Activates a protection group on both clusters where the protection group is configured.

- On the primary cluster only – Secondary cluster remains inactive.

- On the secondary cluster only – Primary cluster remains inactive.

Activating a Hitachi TrueCopy or Universal Replicator protection group on a cluster has the following effect on the data replication layer:

- The data replication configuration of the protection group is validated. During validation, the current local role of a protection group is compared with the aggregate device group state as described in Table 2-3. If validation is successful, data replication is started.

- Data replication is started on the data replication device groups that are configured for the protection group, no matter whether the activation occurs on a primary or secondary cluster. Data is always replicated from the cluster on which the local role of the protection group is `primary` to the cluster on which the local role of the protection group is `secondary`.

Application handling proceeds only after data replication has been started successfully.

Activating a protection group has the following effect on the application layer:

- When a protection group is activated on the primary cluster, the application resource groups that are configured for the protection group are also started.

- When a protection group is activated on the secondary cluster, the application resource groups are not started.

The Hitachi TrueCopy or Universal Replicator command that is used to start data replication depends on the following factors:

- Aggregate device group state

- Local role of the protection group

- Current pair state

If a protection group has a consistency group defined, the fence level is `async` and the device group is in `SMPL` state, then you create the device group with the `paircreate` command when the `geopg start` command is run with the `-f` flag . If a protection group has a consistency group defined, the fence level is not `async` and the device group is in `SMPL` state then you create the device group with the `paircreate` command when you run the `geopg start` command with the `-fg`flags. On arrays that only support the Hitachi TrueCopy software, the `-fg` fence level option to the `geopg` command is not supported. Thus, on such arrays, the user should only define the `ctgid` on the protection group, if that protection group only has device groups of fence level `async`.

The following table describes the Hitachi TrueCopy or Universal Replicator command that is used to start data replication for each of the possible combinations of factors. In the commands, `dg` is the device group name and `fl` is the fence level that is configured for the device group.

Table 2-4 Commands Used to Start Hitachi TrueCopy or Universal Replicator Data Replication

Aggregate Device Group State | Valid Local Protection Group Role | Hitachi TrueCopy or Universal Replicator Start Command
--- | --- | ---
`SMPL` | `primary` or `secondary` | `paircreate -vl -g dg -f fl` `paircreate -vl -g dg -f fl ctgid` `paircreate -vr -g dg -f fl` `paircreate -vr -g dg -f fl ctgid` All commands require that the `horcmd` process is running on the remote cluster. Device pairs can be started with or without a specified CTGID.
`Regular Primary` | `primary` | If the local state code is 22, 23, 25, 26, 29, 42, 43, 45, 46, or 47, no command is run because data is already being replicated. If the local state code is 24, 44, or 48, then the following command is run: `pairresync -g dg [-l]`. If the local state code is 11, then the following command is run: `paircreate -vl -g dg -f fl`. Both commands require that the `horcmd` process is running on the remote cluster.
`Regular Secondary` | `secondary` | If the local state code is 32, 33, 35, 36, 39, 52, 53, 55, 56, or 57, no command is run because data is already being replicated. If the local state code is 34, 54, or 58, then the following command is run: `pairresync -g dg` If the local state code is 11, the following command is run: `paircreate -vr -g dg -f fl` Both commands require that the `horcmd` process is up on the remote cluster.
`Takeover Primary` | `primary` | If the local state code is 34 or 54, the following command is run: `pairresync -swaps -g`. If the local state code is 11, then the following command is run: `paircreate -vl -g dg -f fl`. The `paircreate` command requires that the `horcmd` process is running on the remote cluster.
`Takeover Secondary` | `secondary` | If the local state code is 24, 44, 25, or 45, the following command is run: `pairresync -swapp -g dg`. If the local state code is 11, the following command is run: `paircreate -vr -g dg -f fl`. Both commands require that the `horcmd` process is running on the remote cluster.

## How to Activate a Hitachi TrueCopy or Universal Replicator Protection Group

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. Activate the protection group.

   When you activate a protection group, its application resource groups are also brought online.

       # geopg start -e scope [-n] protectiongroupname

   `-e` scope

     Specifies the scope of the command.

     If the scope is `Local`, then the command operates on the local cluster only. If the scope is `Global`, the command operates on both clusters that deploy the protection group.

     Note - The property values, such as `Global` and `Local`, are not case sensitive.

   `-n`

     Prevents the start of data replication at protection group startup.

     If you omit this option, the data replication subsystem starts at the same time as the protection group.

   protectiongroupname

     Specifies the name of the protection group.

   The `geopg start` command uses Oracle Solaris Cluster commands to bring resource groups and resources online.

Example 2-16 How the Geographic Edition Software Issues the Command to Start Replication

This example illustrates how the Geographic Edition determines the Hitachi TrueCopy or Universal Replicator command that is used to start data replication.

First, the Hitachi TrueCopy or Universal Replicator protection group is created.

    phys-paris-1# geopg create -s paris-newyork-ps -o primary -d truecopy tcpg

A device group, `devgroup1`, is added to the protection group.

    phys-paris-1# geopg add-device-group -p fence_level=async devgroup1 tcpg

The current state of a Hitachi TrueCopy or Universal Replicator device group, `devgroup1`, is provided in the output of the `pairdisplay` command:

    phys-paris-1# pairdisplay -g devgroup1
    Group PairVol(L/R) (Port#,TID,LU),Seq#,LDEV#,P/S,Status,Fence,Seq#,P-LDEV# M
    devgroup1 pair1(L) (CL1-A , 0, 1) 12345   1..SMPL ----  ----, ----- ----   -
    devgroup1 pair1(R) (CL1-C , 0, 20)54321 609..SMPL ----  ----, ----- ----   -
    devgroup1 pair2(L) (CL1-A , 0, 2) 12345   2..SMPL ----  ----, ----- ----   -
    devgroup1 pair2(R) (CL1-C , 0,21) 54321 610..SMPL ----  ----, ----- ----   -

The aggregate device group state is `SMPL`.

Next, the protection group, `tcpg`, is activated by using the `geopg start` command.

    phys-paris-1# geopg start -e local tcpg

The Geographic Edition software runs the `paircreate -g devgroup1 -vl -f async` command at the data replication level. If the command is successful, the state of `devgroup1` is provided in the output of the `pairdisplay` command:

    phys-paris-1# pairdisplay -g devgroup1
    Group PairVol(L/R) (Port#,TID,LU),Seq#,LDEV#,P/S,Status,Fence,Seq#,P-LDEV# M
    devgroup1 pair1(L) (CL1-A , 0, 1) 12345   1..P-VOL COPY ASYNC,54321  609   -
    devgroup1 pair1(R) (CL1-C , 0, 20)54321 609..S-VOL COPY ASYNC,-----   1    -
    devgroup1 pair2(L) (CL1-A , 0, 2) 12345   2..P-VOL COPY ASYNC,54321  610   -
    devgroup1 pair2(R) (CL1-C , 0,21) 54321 610..S-VOL COPY ASYNC,-----   2    -

Example 2-17 Activating a Hitachi TrueCopy or Universal Replicator Protection Group Globally

This example activates a protection group globally.

    # geopg start -e global tcpg

The protection group, `tcpg`, is activated on both clusters where the protection group is configured.

Example 2-18 Activating a Hitachi TrueCopy or Universal Replicator Protection Group Locally

This example activates a protection group on a local cluster only. This local cluster might be a primary cluster or a secondary cluster, depending on the role of the cluster.

    # geopg start -e local tcpg

Copyright © 2004, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |