HP XP P9500 Storage User Manual
Page 85
![background image](/manuals/398260/85/background.png)
oradb2 oradev22(R) (CL1-D , 2, 2-1)30053 269..SMPL ----,----- ---- -
oradb oradev2(R) (CL1-D , 2, 2) 30053 269..S-VOL PAIR,----- 267 -
Configuration definition for cascading volume pairs
The RAID Manager software (HORCM) is capable of keeping track of up to seven pair associations
per LDEV (1 for Cnt Ac-S/Cnt Ac-J, 3 for Cnt Ac-J, 3 for BC/Snapshot, 1 for Snapshot). By this
management, RAID Manager can be assigned to seven groups per LU that describes seven mirror
descriptors for a configuration definition file.
Figure 25 Mirror descriptors and group assignment
Correspondence of the configuration file and mirror descriptors
The group name and MU# which are described in HORCM_DEV of a configuration definition file
are assigned the corresponding mirror descriptors, as outlined in
. “Omission
of MU#” is handled as MU#0, and the specified group is registered to MU#0 on Business Copy
and Continuous Access Synchronous. Also, the MU# that is noted for HORCM_DEV in
reflects a random numbering sequence (for example, 2, 1, 0).
Table 18 Mirror descriptors and group assignments
Continuous
Access
Business Copy
(Snapshot) only
MU#0
HORCM_DEV parameter in configuration file
Journal
only
MU#1-#3
MU#1-#2
Business Copy
Continuous
Access
(MU#3-#63)
Synchronous/
Continuous
Access
Journal
-
-
oradev1
oradev1
HORCM_DEV
#dev_group dev_name port# TargetID
LU# MU#
Oradb oradev1 CL1-D 2
1
-
oradev11
oradev1
oradev1
HORCM_DEV
oradev21
#dev_group dev_name port# TargetID
LU# MU#
Oradb oradev1 CL1-D 2
1
Oradb1 oradev11 CL1-D 2
1 1
Oradb2 oradev21 CL1-D 2
1 2
Examples of RAID Manager configurations
85