JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster System Administration Guide     Oracle Solaris Cluster
search filter icon
search icon

Document Information

Preface

1.  Introduction to Administering Oracle Solaris Cluster

2.  Oracle Solaris Cluster and RBAC

3.  Shutting Down and Booting a Cluster

4.  Data Replication Approaches

5.  Administering Global Devices, Disk-Path Monitoring, and Cluster File Systems

6.  Administering Quorum

7.  Administering Cluster Interconnects and Public Networks

8.  Adding and Removing a Node

9.  Administering the Cluster

10.  Configuring Control of CPU Usage

11.  Patching Oracle Solaris Cluster Software and Firmware

12.  Backing Up and Restoring a Cluster

13.  Administering Oracle Solaris Cluster With the Graphical User Interfaces

A.  Example

Configuring Host-Based Data Replication With Sun StorageTek Availability Suite Software

Understanding Sun StorageTek Availability Suite Software in a Cluster

Data Replication Methods Used by Sun StorageTek Availability Suite Software

Remote Mirror Replication

Point-in-Time Snapshot

Replication in the Example Configuration

Guidelines for Configuring Host-Based Data Replication Between Clusters

Configuring Replication Resource Groups

Configuring Application Resource Groups

Configuring Resource Groups for a Failover Application

Configuring Resource Groups for a Scalable Application

Guidelines for Managing a Failover

Task Map: Example of a Data Replication Configuration

Connecting and Installing the Clusters

Example of How to Configure Device Groups and Resource Groups

How to Configure a Device Group on the Primary Cluster

How to Configure a Device Group on the Secondary Cluster

How to Configure the File System on the Primary Cluster for the NFS Application

How to Configure the File System on the Secondary Cluster for the NFS Application

How to Create a Replication Resource Group on the Primary Cluster

How to Create a Replication Resource Group on the Secondary Cluster

How to Create an NFS Application Resource Group on the Primary Cluster

How to Create an NFS Application Resource Group on the Secondary Cluster

Example of How to Enable Data Replication

How to Enable Replication on the Primary Cluster

How to Enable Replication on the Secondary Cluster

Example of How to Perform Data Replication

How to Perform a Remote Mirror Replication

How to Perform a Point-in-Time Snapshot

How to Verify That Replication Is Configured Correctly

Example of How to Manage a Failover

How to Provoke a Switchover

How to Update the DNS Entry

Index

How to Enable Replication on the Primary Cluster

  1. Access nodeA as superuser or assume a role that provides solaris.cluster.read RBAC authorization.
  2. Flush all transactions.
    nodeA# lockfs -a -f
  3. Confirm that the logical host names lhost-reprg-prim and lhost-reprg-sec are online.
    nodeA# clresourcegroup status
    nodeC# clresourcegroup status

    Examine the state field of the resource group.

  4. Enable remote mirror replication from the primary cluster to the secondary cluster.

    This step enables replication from the master volume on the primary cluster to the master volume on the secondary cluster. In addition, this step enables replication to the remote mirror bitmap on vol04.

    • If the primary cluster and secondary cluster are unsynchronized, run this command for Sun StorageTek Availability Suite software:

      nodeA# /usr/sbin/sndradm -n -e lhost-reprg-prim \
      /dev/vx/rdsk/devgrp/vol01 \
      /dev/vx/rdsk/devgrp/vol04 lhost-reprg-sec \
      /dev/vx/rdsk/devgrp/vol01 \
      /dev/vx/rdsk/devgrp/vol04 ip sync
    • If the primary cluster and secondary cluster are synchronized, run this command for Sun StorageTek Availability Suite software:

      nodeA# /usr/sbin/sndradm -n -E lhost-reprg-prim \
      /dev/vx/rdsk/devgrp/vol01 \
      /dev/vx/rdsk/devgrp/vol04 lhost-reprg-sec \
      /dev/vx/rdsk/devgrp/vol01 \
      /dev/vx/rdsk/devgrp/vol04 ip sync
  5. Enable autosynchronization.

    Run this command for Sun StorageTek Availability Suite software:

    nodeA# /usr/sbin/sndradm -n -a on lhost-reprg-prim \
    /dev/vx/rdsk/devgrp/vol01 \
    /dev/vx/rdsk/devgrp/vol04 lhost-reprg-sec \
    /dev/vx/rdsk/devgrp/vol01 \
    /dev/vx/rdsk/devgrp/vol04 ip sync

    This step enables autosynchronization. When the active state of autosynchronization is set to on, the volume sets are resynchronized if the system reboots or a failure occurs.

  6. Verify that the cluster is in logging mode.

    Use the following command for Sun StorageTek Availability Suite software:

    nodeA# /usr/sbin/sndradm -P

    The output should resemble the following:

    /dev/vx/rdsk/devgrp/vol01 ->
    lhost-reprg-sec:/dev/vx/rdsk/devgrp/vol01
    autosync: off, max q writes:4194304, max q fbas:16384, mode:sync,ctag:
    devgrp, state: logging

    In logging mode, the state is logging, and the active state of autosynchronization is off. When the data volume on the disk is written to, the bitmap file on the same disk is updated.

  7. Enable point-in-time snapshot.

    Use the following command for Sun StorageTek Availability Suite software:

    nodeA# /usr/sbin/iiadm -e ind \
    /dev/vx/rdsk/devgrp/vol01 \
    /dev/vx/rdsk/devgrp/vol02 \
    /dev/vx/rdsk/devgrp/vol03
    nodeA# /usr/sbin/iiadm -w \
    /dev/vx/rdsk/devgrp/vol02

    This step enables the master volume on the primary cluster to be copied to the shadow volume on the same cluster. The master volume, shadow volume, and point-in-time bitmap volume must be in the same device group. In this example, the master volume is vol01, the shadow volume is vol02, and the point-in-time bitmap volume is vol03.

  8. Attach the point-in-time snapshot to the remote mirror set.

    Use the following command for Sun StorageTek Availability Suite software:

    nodeA# /usr/sbin/sndradm -I a \
    /dev/vx/rdsk/devgrp/vol01 \
    /dev/vx/rdsk/devgrp/vol02 \
    /dev/vx/rdsk/devgrp/vol03

    This step associates the point-in-time snapshot with the remote mirror volume set. Sun StorageTek Availability Suite software ensures that a point-in-time snapshot is taken before remote mirror replication can occur.

Next Steps

Go to How to Enable Replication on the Secondary Cluster.