Sun Storage 9980 System
 

PLA-Support>Sun Systems>DISK>HighEnd Arrays>SN-DK: HDS_99xx
 
.Old GCS Categories>Sun Microsystems>Storage - Disk>Datacenter Disk
 

Applies to:

Goal

 This article is an introduction to HDS Shadow Image features and CCI (Raid Manager). It provides an overview of the horcm.conf configuration files.

Fix

HDS Shadow Image is used to duplicate volumes internally inside a subsystem.
Raid Manager (CCI) is a software package that provides a management method of controlling shadow image environment. CCI enables users to perform Hitachi open shadow image (HOMRCF) operations by issuing commands from a Solaris[TM] host or a PC. CCI manages the HORC and HORCM configuration files and instances.

Files horcm0.conf and horcm1.conf have to be defined in a very accurate way to make it run.

Here, the goal is to duplicate a volume 9 times via Shadow Image:

+------ S-VOL/P-VOL +------ S-VOL : 0-111
| vg10     0-110        | vg11
|                             +------ S-VOL : 0-112
|                               vg12
|
P-VOL  ---+------ S-VOL/P-VOL +------ S-VOL : 0-121
 0-100     | vg20         0-120    | vg21
|                                           +------ S-VOL : 0-122
|                                             vg22
|
+------ S-VOL/P-VOL +------ S-VOL : 0-131
      vg30     0-130    | vg31
                              +------ S-VOL : 0-132
                                vg32

Where

P-VOL : Primary volume: source
S-VOL : Secondary volume : destination
vgxx : Branch instance used as dev_name in horcmX.conf files.
This represents a paired logical volume.
0-130 : Target 0, LUN 130. Values based upon format command on server
(c2t0d130s2). Used as targetID and LU# in horcmX.conf files.

P-VOL 0-100 is duplicated on S-VOL 0-110. Then S-VOL 0-110 becomes P-VOL
0-110 for another copy to S-VOL 0-111.

Raid Manager (HORCM) configuration files describe the following:
-Communication path between Primary and Secondary server HORCM instances
-HORCM command device address
-LUNs by individual name and by group

Note -

All the source volumes should be in horcm0.conf and all the destination volumes should be in horcm1.conf.

The horcm0.conf and horcm1.conf files follow:
------------------------------------------------
::::::::::::::
horcm0.conf
::::::::::::::
HORCM_MON
#ip_address service poll(10ms) timeout(10ms)
physporgyh horcm0 1000 3000

HORCM_CMD
#dev_name dev_name dev_name
/dev/rdsk/c2t0d119s2

HORCM_DEV
#dev_group dev_name port# TargetID LU# MU#
annacp1 vg10 cl1-a 0 100 0
annacp1 vg20 cl1-a 0 100 1
annacp1 vg30 cl1-a 0 100 2

annacp2 vg11 cl1-e 0 110 1
annacp2 vg12 cl1-e 0 110 2
annacp2 vg21 cl1-e 0 120 1
annacp2 vg22 cl1-e 0 120 2
annacp2 vg31 cl1-e 0 130 1
annacp2 vg32 cl1-e 0 130 2

HORCM_INST
#dev_group ip_address service
annacp1 physporgyh horcm1
annacp2 physporgyh horcm1

::::::::::::::
horcm1.conf
::::::::::::::
HORCM_MON
#ip_address service poll(10ms) timeout(10ms)
physporgyh horcm1 1000 3000

HORCM_CMD
#dev_name dev_name dev_name
/dev/rdsk/c2t0d119s2

HORCM_DEV
#dev_group dev_name port# TargetID LU# MU#
annacp1 vg10 cl1-e 0 110 0
annacp1 vg20 cl1-e 0 120 0
annacp1 vg30 cl1-e 0 130 0

annacp2 vg11 cl1-e 0 111 0
annacp2 vg12 cl1-e 0 112 0
annacp2 vg21 cl1-e 0 121 0
annacp2 vg22 cl1-e 0 122 0
annacp2 vg31 cl1-e 0 131 0
annacp2 vg32 cl1-e 0 132 0

HORCM_INST
#dev_group ip_address service
annacp1 physporgyh horcm0
annacp2 physporgyh horcm0

Note : MU# is the branch copy number.
dev_group allows to gather multiple "paired logical volumes"

The following commands have to be executed to create pairs:

# HORCC_MRCF=1; export HORCC_MRCF # required for shadow Image only
# HORCMINST=0
# export HORCMINST
# paircreate -g annacp1 -vl	# copy : 100->110, 100->120, 100->130	
# paircreate -g annacp2 -vl	# copy : 110->111/112, 120->121/122,
130->131/132

It is also possible to specify a dev_name (paired logical volume) in order to copy one branch at one and the same time:

 # paircreate -g annacp1 -vl -d vg10	# copy : 100->110 only

Note: the value of the environment variable HORCMINST and HORCC_MRCF have great importance for CCI/Raid Manager activity.

To switch CCI from True Copy to Shadow Image, HORCC_MRCF should be set to 1 prior to invoking commands.

HORCMINST details which .conf file to use. If no HORCMINST is set then horcm.conf is used. HORCMINST=0 will use horcm0.conf , HORCMINST=1 will use horcm1.conf

Caution should be taken when using CCI commands and in particular paircreate.
If the wrong HORCMINST value is set or the wrong command line arguments are used, the copy direction may not be as anticipated.

Product
Sun StorageTek 9900 ShadowImage In-System Replication

Internal Comments
Documentation for Shadow Image and True Copy can be found at:

http://pts-storage.us.oracle.com/products/T99x0/documentation.html
HDS, shadowimage, paircreate, HORCMINST, horc, horcm, si
Previously Published As
70461

Change History
Date: 2006-03-09
User Name: 7058
Action: Approved
Comment: Added 1 trademark and fixed 1 grammar glitch (plural word to singular).
Updated review date.
OK to republish.
Version: 8
Date: 2006-03-08
User Name: 7058
Action: Accept
Comment:
Version: 0
Date: 2006-03-08
User Name: 117992
Action: Approved
Comment: document is accurate. Reviewed changes made by updater. forwarding to final review.
Version: 0
Product_uuid
590124a6-1b6f-4082-bb2c-c8d209ec464a|Sun StorageTek 9900 ShadowImage In-System Replication

This solution has no attachment