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

Strategies for Creating Hitachi TrueCopy and Universal Replicator Protection Groups

Creating a Protection Group While the Application Is Offline

Creating a Protection Group While the Application Is Online

Creating, Modifying, Validating, and Deleting a Hitachi TrueCopy or Universal Replicator Protection Group

How to Create and Configure a Hitachi TrueCopy or Universal Replicator Protection Group That Does Not Use Oracle Real Application Clusters

Ensuring Data Consistency for Hitachi Universal Replicator in Asynchronous Mode

Understanding Data Consistency in Geographic Edition

Using Consistency Group IDs to Ensure Data Consistency

Requirements to Support Oracle Real Application Clusters With Data Replication Software

How to Create a Protection Group for Oracle Real Application Clusters

How the Data Replication Subsystem Validates the Device Group

How to Modify a Hitachi TrueCopy or Universal Replicator Protection Group

Validating a Hitachi TrueCopy or Universal Replicator Protection Group

How to Validate a Hitachi TrueCopy or Universal Replicator Protection Group

How to Delete a Hitachi TrueCopy or Universal Replicator Protection Group

Administering Hitachi TrueCopy and Universal Replicator Application Resource Groups

How to Add an Application Resource Group to a Hitachi TrueCopy or Universal Replicator Protection Group

How to Delete an Application Resource Group From a Hitachi TrueCopy or Universal Replicator Protection Group

Administering Hitachi TrueCopy and Universal Replicator Data Replication Device Groups

How to Add a Data Replication Device Group to a Hitachi TrueCopy or Universal Replicator Protection Group

Validations Made by the Data Replication Subsystem

How the State of the Hitachi TrueCopy or Universal Replicator Device Group Is Validated

Determining the State of an Individual Hitachi TrueCopy or Universal Replicator Device Group

Determining the Aggregate Hitachi TrueCopy or Universal Replicator Device Group State

Validating the Local Role of the Protection Group Against the Aggregate Device Group State

How to Modify a Hitachi TrueCopy or Universal Replicator Data Replication Device Group

How to Delete a Data Replication Device Group From a Hitachi TrueCopy or Universal Replicator Protection Group

Replicating the Hitachi TrueCopy or Universal Replicator Protection Group Configuration to a Secondary Cluster

How to Replicate the Hitachi TrueCopy or Universal Replicator Protection Group Configuration to a Secondary Cluster

Activating a Hitachi TrueCopy or Universal Replicator Protection Group

How to Activate a Hitachi TrueCopy or Universal Replicator Protection Group

Deactivating a Hitachi TrueCopy or Universal Replicator Protection Group

How to Deactivate a Hitachi TrueCopy or Universal Replicator Protection Group

Resynchronizing a Hitachi TrueCopy or Universal Replicator Protection Group

How to Resynchronize a Protection Group

Checking the Runtime Status of Hitachi TrueCopy and Universal Replicator Data Replication

Displaying a Hitachi TrueCopy or Universal Replicator Runtime Status Overview

How to Check the Overall Runtime Status of Replication

Displaying a Detailed Hitachi TrueCopy or Universal Replicator Runtime Status

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

A.  Geographic Edition Properties for Hitachi TrueCopy and Universal Replicator

Index

Checking the Runtime Status of Hitachi TrueCopy and Universal Replicator Data Replication

You can obtain an overall view of the status of replication, as well as a more detailed runtime status of the Hitachi TrueCopy or Universal Replicator replication resource groups. The following sections describe the procedures for checking each status.

Displaying a Hitachi TrueCopy or Universal Replicator Runtime Status Overview

The status of each Hitachi TrueCopy or Universal Replicator data replication resource indicates the status of replication on a particular device group. The status of all the resources under a protection group are aggregated in the replication status. This replication status is the second component of the protection group state. For more information about the states of protection groups, refer to Monitoring the Runtime Status of the Geographic Edition Software in Oracle Solaris Cluster Geographic Edition System Administration Guide.

To view the overall status of replication, look at the protection group state as described in the following procedure.

How to Check the Overall Runtime Status of Replication

  1. Access a node of the cluster where the protection group has been defined.

    You must be assigned the Basic Solaris User 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. Check the runtime status of replication.
    # geoadm status

    Refer to the Protection Group section of the output for replication information. The information that is displayed by this command includes the following:

    • Whether the local cluster is enabled for partnership participation

    • Whether the local cluster is involved in a partnership

    • Status of the heartbeat configuration

    • Status of the defined protection groups

    • Status of current transactions

  3. Check the runtime status of data replication for each Hitachi TrueCopy or Universal Replicator device group.
    # clresource status

    Refer to the Status and Status Message fields for the data replication device group you want to check.

See Also

For more information about these fields, see Table 2-6.

Displaying a Detailed Hitachi TrueCopy or Universal Replicator Runtime Status

The Geographic Edition software internally creates and maintains one replication resource group for each protection group. The name of the replication resource group has the following format:

rg-tc_truecopyprotectiongroupname

If you add a Hitachi TrueCopy or Universal Replicator device group to a protection group, Geographic Edition software creates a resource for each device group. This resource monitors the status of replication for its device group. The name of each resource has the following format:

r-tc-truecopyprotectiongroupname-truecopydevicegroupname

You can monitor the status of replication of this device group by checking the Status and Status Message of this resource. Use the clresource status command to display the resource status and the status message.

The following table describes the Status and Status Message values that are returned by the clresource status command when the State of the Hitachi TrueCopy or Universal Replicator replication resource group is Online.

Table 2-6 Status and Status Messages of an Online Hitachi TrueCopy or Universal Replicator Replication Resource Group

Status
Status Message
Online
P-Vol/S-Vol:PAIR
Online
P-Vol/S-Vol:PAIR:Remote horcmd not reachable
Online
P-Vol/S-Vol:PFUL
Online
P-Vol/S-Vol:PFUL:Remote horcmd not reachable
Degraded
SMPL:SMPL
Degraded
SMPL:SMPL:Remote horcmd not reachable
Degraded
P-Vol/S-Vol:COPY
Degraded
P-Vol/S-Vol:COPY:Remote horcmd not reachable
Degraded
P-Vol/S-Vol:PSUS
Degraded
P-Vol/S-Vol:PSUS:Remote horcmd not reachable
Degraded
P-Vol/S-Vol:PFUS
Degraded
P-Vol/S-Vol:PFUS:Remote horcmd not reachable
Faulted
P-Vol/S-Vol:PDFUB
Faulted
P-Vol/S-Vol:PDUB:Remote horcmd not reachable
Faulted
P-Vol/S-Vol:PSUE
Faulted
P-Vol/S-Vol:PSUE:Remote horcmd not reachable
Degraded
S-Vol:SSWS:Takeover Volumes
Faulted
P-Vol/S-Vol:Suspicious role configuration. Actual Role=x, Config Role=y

For more information about these values, refer to the Hitachi TrueCopy or Universal Replicator documentation.

For more information about the clresource status command, see the clresource(1CL) man page.