Scribd
Upload
214 views2 pages

HDS ShadowImage

This document provides a quick guide for configuring HDS ShadowImage on a storage system. It outlines the steps to allocate physical and shadow volumes, create pairs, and configure the host including editing configuration files and starting the HORCM daemon to access the shadow volumes. It also provides details on consistency groups and performing an initial establish for a new shadow image configuration.

Uploaded by

Marcelo Ariza
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
214 views2 pages

HDS ShadowImage

This document provides a quick guide for configuring HDS ShadowImage on a storage system. It outlines the steps to allocate physical and shadow volumes, create pairs, and configure the host including editing configuration files and starting the HORCM daemon to access the shadow volumes. It also provides details on consistency groups and performing an initial establish for a new shadow image configuration.

Uploaded by

Marcelo Ariza
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

HDS ShadowImage

QuickReference
Overview
Other Usefull Commands

Author: Rodrigo Dias E-Mail: [email protected] Office: BRGDC San Team

This document is a quick guide for HDS Shadow Image configuration.


[Sudo Access is required]

Steps to be done on the Storage Frame


Allocate luns for PVOL and SVOL n On Storage navigator screen , Click icon lun manager n Select the port where the server attached to n Select ldev # (make sure the ldev not belong to any port by looking at column path) n Click add path and apply Repeat the above step for every SVOL allocation Paircreate n Select PVOL server port n Select PVOL server hostgroup n Hightlight PVOL to pair n Right Click and select paircreate n Select SVOL port and select SVOL to pair n Select Set n ok and Apply.

n n n n n n n n n

Stop HORCM: sudo horcmshutdown.sh 0 1 Start HORCM: horcmstart.sh 0 1 Display a given device group: pairdisplay g s1-vg_rpas fcx Display all devices allocated to array port:: raidscan p <port#> Show group CTGID: sudo pairdisplay -g s1-vg_CODS10P1 fe |more Show Volume status: sudo pairvolchk -g s1-vg_CODS10P1 d ldev-a8c-309 Show pair status with % completed: sudo pairdisplay -g s1vg_CODS10P1 -fcx Remove from a group: pairsplit -S -g group -d ldev_xxx_xxx Execute the full sync: paircreate g s1-vg_CODS10P1 -d ldev_xxx_xxx -m grp 08 -vl

Steps to be done on the host that will access the ShadowImage Volumes
n n The configuration files are located on: /opt/HORCM/etc Create a backup of the actual configuration files:
horcm0.conf hormc1.conf (Standard Volumes) (Shadow Image Volumes)

To get the TargetID and LU#


ro734uq@pnbumm01> sudo raidscan -p CL1-H -fx | grep 149 CL1-H CL1-H CL1-H CL1-H CL1-H CL1-H /d4/ /d4/ /d4/ /d4/ /d4/ /d4/ 0,11, 0,11, 0,11, 0,11, 0,11, 0,11, 7-0 7-1 7-2 40-0 40-1 40-2 .1(149)...........P-VOL .1(149)...........SMPL .1(149)...........SMPL .1(149)...........P-VOL .1(149)...........SMPL .1(149)...........SMPL PSUS ------PSUS ------149, -----, -----, 149, -----, -----, 43514 --------43514 --------983 --------983 ---------

Edit each file accordingly and add the new entries as shown in the example below:
horcm0.conf
#dev_group s1-vg_rpas s1-vg_rpas s1-vg_rpas dev_name ldev-149-983 ldev-14a-984 ldev-14b-985 dev_name port# CL1-H CL1-H CL1-H port# TargetID 0 0 0 TargetID LU# 7 8 9 MU# STD-SI

horcm1.conf
#dev_group LU# MU#

QuickReference

s1-vg_rpas s1-vg_rpas s1-vg_rpas

ldev-149-983 ldev-14a-984 ldev-14b-985

CL1-B CL1-B CL1-B

0 0 0

1 2 3

Legend: dev_group - Defines a group of Pvols and Svols devices. dev_name - Logical name that describes both Pvol Ldev and Svol Ldev. port# - Defines the port in which the device is allocated to. TargetID - Default setting set to 0 for IBM. LU# - Logical Unit or Ldev that was allocated down the port. MU# - Defines a a mirror unit.

n n

Save the files Check if HORCM daemon is running


example: ps ef | grep ho ro734uq@pnbumm01:/home/users/tchrbw1> ps -ef | grep ho root 270552 1 0 Dec 02 - 0:31 horcmd_01 root 385256 1 0 Dec 02 - 0:40 horcmd_00

n n

Stop HORCM: sudo horcmshutdown.sh 0 1 Start HORCM: horcmstart.sh 0 1

For a new consistency group n n If will be a new ShadowImage Group: Each dev_group group also belongs to a Consistency group.By creating these consistency groups ShadowImage guarantees data consistency among multiple LUNs in a group at a single point in time when doing a split using the pairsplit g <group> command. See consistance groups in the conf files:
Consistency Groups Documentation si-rpas = 0 si-rdf01 = 1 s1-share01dg = 2 s1-share02dg = 3 s1-share03dg = 4 s2-share01dg = 5 s2-share02dg = 6 s2-share03dg = 7

n
# # # # # # # # #

n n

Use next available number for new groups. Next edit the conf file on /HORCM/scripts/conf One config file per mirror number. First line is the host or hosts the ShadowImage devices will mount to. No other information is required. Example:
pnbumm01 > more share02dg-1.conf pnbumm01

If you build something new you have to do a full establish first and have to pass the group:
/HORCM/scripts/bin/initial_bcv_establish.ksh -g <group_name> Ex: sudo /HORCM/scripts/bin/initial_bcv_establish.ksh -g share02dg-1.conf

QuickReference

You might also like