Filter
Top Products
302 Chapter 4 Performing CCI Operations
(2) pairdisplay
-f[d]. The -f[d] option shows the relation between the Device_File and the paired volumes
(protected volumes and permitted volumes), based on the group, even though this option
does not have any relation with protection mode.
# pairdisplay -g oradb -fd
Group PairVol(L/R) Device_File M ,Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M
oradb oradev1(L) c0t3d0 0 35013 17..P-VOL COPY, 35013 18 -
oradb oradev1(R) c0t3d1 0 35013 18..S-VOL COPY, 35013 17 -
If either the local or the remote host (instance) has not been shown the Device_File, then
pair operation are rejected (except the local option such as “-l”) in protection mode
because of Unknown volume, as shown in the following example.
# pairdisplay -g oradb -fd
Group PairVol(L/R) Device_File M ,Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M
oradb oradev1(L) c0t3d0 0 35013 17..P-VOL COPY, 35013 18 -
oradb oradev1(R) Unknown 0 35013 ****..---- ----, ----- ---- -
4.16.6 Permitting the Protected Volumes
Protection Mode needs recognition step to check accessible volumes and horcm.conf at the
startup of HORCM on protection mode. The protected volumes must be registered to enable
Protection Facility at each startup of HORCM, so that this registration process is executed
automatically by /etc/horcmgr (see (1) and (2) below).
(1) The following is executed for registration of permitted volume file ($HORCMPERM file), if
$HORCMPERM file is existing and there are permitted volumes. If the user wants to permit
only the volumes specified, then the volume list must be described in $HORCMPERM file.
Naming of $HORCMPERM file:
UNIX systems. $HORCMPERM is “/etc/horcmperm.conf” or “/etc/horcmperm*.conf”
(* is the instance number) as default. Example for HP-UX systems:
cat $HORCMPERM | /HORCM/usr/bin/raidscan -find inst
# The following are an example to permit the LVM Volume groups.
# For MU# 0
vg00 /dev/rdsk/c0t3d0 /dev/rdsk/c0t3d1
vg00 /dev/rdsk/c0t3d2 /dev/rdsk/c0t3d3
# For MU# 1
vg01 /dev/rdsk/c0t3d0 /dev/rdsk/c0t3d1
vg01 /dev/rdsk/c0t3d2 /dev/rdsk/c0t3d3
.
Verifying a group for vg01. The following are examples to verify whether LVM volume
group is mapped to group (MU#1 for ShadowImage) on the horcm.conf correctly.
# export HORCC_MRCF=1
# cat /etc/horcmperm.conf | grep vg01 | raidscan -find verify 1 -fd
OR
# vgdisplay -v /dev/vg01|grep dsk|sed 's/\/*\/dsk\//\/rdsk\//g'|raidscan -find verify 1 -fd
DEVICE_FILE Group PairVol Device_File M SERIAL LDEV
/dev/rdsk/c0t3d0 oradb1 oradev1 c0t3d0 1 35013 17
/dev/rdsk/c0t3d1 oradb1 oradev2 c0t3d1 1 35013 18
/dev/rdsk/c0t3d2 oradb oradev3 c0t3d2 1 35013 19
/dev/rdsk/c0t3d3 - - - 1 35013 20
Mapping to another group on horcm.conf !!
Unknown on horcm.conf !!