Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access for P9000 and XP A.11.00

Figure 41 Multi-Hop Bi-Link (1:1:1)
Array
Datacenter 1
Node A Node B Node C
Datacenter 2 Datacenter 3
Array Array
#0
#2
#0
#1 #1
#2
P-VOL S/P S-VOL
MU# h2
dg 13(Phantom Device Group)
P-Jnl
S-Jnl
CA Sync
MU#
omitted
dg 12
MU# h1
dg 23
CA Journal
Sample Raid Manager Configuration on a DC1 NodeA (multi-hop-Bi-Link)
HORCM _MON
#ip_address service poll(10ms) timeout(10ms)
NodeA horcm0 1000 3000
HORCM_CMD
#dev_name dev_name dev_name
/dev/rdsk/c6t12d0 /dev/rdsk/c9t12d0
HORCM_DEV
#dev_group dev_name port# TargetID LU# MU#
dg12 dg12_d0 CL3-E 6 5
#Phantom device group dg13
dg13 dg13_d0 CL3-E 6 5 h2
HORCM _INST
#dev_group ip_address service
dg12 NodeB.dc2.net horcm0 # communicate with DC2 nodes
dg13 NodeC.dc3.net horcm0 # communicate with DC3 nodes
Sample Raid Manager Configuration on a DC2 NodeB (multi-hop-Bi-Link)
HORCM _MON
#ip_address service poll(10ms) timeout(10ms)
NodeB horcm0 1000 3000
HORCM_CMD
#dev_name dev_name dev_name
/dev/rdsk/c21t8d0 /dev/rdsk/c24t8d0
HORCM_DEV
#dev_group dev_name port# TargetID LU# MU#
dg12 dg12_d0 CL1-A 13 1
dg23 dg23_d0 CL1-A 13 1 h1
HORCM _INST
#dev_group ip_address service
dg12 NodeA.dc1.net horcm0 # communicate with DC1 nodes
dg23 NodeC.dc3.net horcm0 # communicate with DC3 nodes
Configuring an application 113