test

Sun Cluster Geographic Edition System Administration Guide

Configuring Data Replication With Hitachi TrueCopy Software on the Primary Cluster

This section describes the steps you must perform on the primary cluster before you can configure Hitachi TrueCopy data replication in Sun Cluster Geographic Edition software. To illustrate each step, this section uses an example of two disks, or LUNs, that are called d1 and d2. These disks are in a Hitachi TrueCopy array that holds data for an application that is called apprg1.

Configuring the /etc/horcm.conf File

First, configure the Hitachi TrueCopy device groups on shared disks in the primary cluster. Disks d1 and d2 are configured to belong to a Hitachi TrueCopy device group that is called devgroup1. This configuration information is specified in the /etc/horcm.conf file on each of the cluster's nodes that has access to the Hitachi array. The application, apprg1, can run on these cluster nodes.

For more information about how to configure the /etc/horcm.conf file, see the Sun StorEdge SE 9900 V Series Command and Control Interface User and Reference Guide.

The following table describes the configuration information from our example that is found in the /etc/horcm.conf file.

Table 9–2 Example Section of the /etc/horcm.conf File on the Primary Cluster

dev_group

dev_name

port number

TargetID

LU number

MU number

devgroup1

pair1

CL1–A

0

1

 

devgroup1

pair2

CL1–A

0

2

 

The configuration information in the table indicates that the Hitachi TrueCopy device group, devgroup1, contains two pairs. The first pair, pair1, is from the d1 disk, which is identified by the tuple <CL1–A , 0, 1>. The second pair, pair2, is from the d2 disk and is identified by the tuple <CL1–A, 0, 2>. The replicas of disks d1 and d2 are located in a geographically separated Hitachi TrueCopy array. The remote Hitachi TrueCopy is connected to the partner cluster.

ProcedureHow to Configure the Volumes for Use With Hitachi TrueCopy Replication

Hitachi TrueCopy supports VERITAS Volume Manager volumes. You must configure VERITAS Volume Manager volumes on disks d1 and d2.

Caution – Caution –

If you are using storage-based replication, do not configure a replicated volume as a quorum device. The Sun Cluster Geographic Edition software does not support Hitachi TrueCopy S-VOL and Command Device as a Sun Cluster quorum device. See Using Storage-Based Data Replication in Sun Cluster 3.0-3.1 Hardware Administration Manual for Solaris OS for more information.

Steps

  1. Create VERITAS Volume Manager disk groups on shared disks in cluster-paris.

    For example, the d1 and d2 disks are configured as part of a VERITAS Volume Manager disk group, which is called oradg1, by using commands, such as vxdiskadm and vxdg.

  2. After configuration is complete, verify that the disk group was created by using the vxdg list command.

    The output of this command should show oradg1 as a disk group.

  3. Create the VERITAS Volume Manager volume.

    For example, a volume that is called vol1 is created in the oradg1 disk group. The appropriate VERITAS Volume Manager commands, such as vxassist, are used to configure the volume.

ProcedureHow to Configure the Sun Cluster Device Group That Is Controlled by Hitachi TrueCopy

Before You Begin

If you are using storage-based replication, do not configure a replicated volume as a quorum device. The Sun Cluster Geographic Edition software does not support Hitachi TrueCopy S-VOL and Command Device as a Sun Cluster quorum device. See Using Storage-Based Data Replication in Sun Cluster 3.0-3.1 Hardware Administration Manual for Solaris OS for more information.

Steps

  1. Register the VERITAS Volume Manager disk group that you configured in the previous procedure.

    Use the Sun Cluster commands, scsetup or scconf.

    For more information about these commands, refer to the scsetup(1M) or the scconf(1M) man page.

  2. Synchronize the VERITAS Volume Manager configuration with Sun Cluster software, again by using the scsetup or scconf commands.

  3. After configuration is complete, verify the disk group registration. 


    # scstat -D

    The VERITAS Volume Manager disk group, oradg1, should be displayed in the output.

    For more information about the scstat command, see the scstat(1M) man page.

ProcedureHow to Configure a Highly Available File System for Hitachi TrueCopy Replication

Before You Begin

Before you configure the file system on cluster-paris, ensure that the Sun Cluster entities you require, such as application resource groups, device groups, and mount points, have already been configured.

If you are using storage-based replication, do not configure a replicated volume as a quorum device. The Sun Cluster Geographic Edition software does not support Hitachi TrueCopy S-VOL and Command Device as a Sun Cluster quorum device. See Using Storage-Based Data Replication in Sun Cluster 3.0-3.1 Hardware Administration Manual for Solaris OS for more information.

Steps

  1. Create the required file system on the vol1 volume at the command line.

  2. Add an entry to the /etc/vfstab file that contains information such as the mount location.

    Whether the file system is to be mounted locally or globally depends on various factors, such as your performance requirements, or the type of application resource group you are using.

    Note –

    You must set the mount at boot field in this file to no. This value prevents the file system from mounting on the secondary cluster at cluster startup. Instead, the Sun Cluster software and the Sun Cluster Geographic Edition framework handle mounting the file system by using the HAStoragePlus resource when the application is brought online on the primary cluster. Data must not be mounted on the secondary cluster or data on the primary will not be replicated to the secondary cluster. Otherwise, the data will not be replicated from the primary cluster to the secondary cluster.

  3. Add the HAStoragePlus resource to the application resource group, apprg1.

    Adding the resource to the application resource group ensures that the necessary file systems are remounted before the application is brought online.

    For more information about the HAStoragePlus resource type, refer to the Sun Cluster 3.1 Data Service Planning and Administration Guide.

Example 9–1 Configuring a Highly Available Cluster Global File System

This example assumes that the apprg1 resource group already exists.

  1. Create a UNIX file system (UFS).


    # newfs dev/vx/dsk/oradg1/vol1

  2. An entry in the /etc/vfstab file is created as follows:


    # /dev/vs/dsk/oradg1/vol1 /dev/vx/rdsk/oradg1/vol1 /mounts/sample 
ufs 2 no logging

  3. Add the HAStoragePlus resource type. 


    # scrgadm -a -j rs-hasp -g apprg1 -t SUNW.HAStoragePlus 
-x FilesystemMountPoints=/mounts/sample -x AffinityOn=TRUE 
-x GlobalDevicePaths=oradg1