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

Sample Raid Manager Configuration on a DC3 NodeC (multi-hop-Bi-Link)
HORCM _MON
#ip_address service poll(10ms) timeout(10ms)
NodeC horcm0 1000 3000
HORCM_CMD
#dev_name dev_name dev_name
/dev/rdsk/c6t2d0 /dev/rdsk/c8t2d0
HORCM_DEV
#dev_group dev_name port# TargetID LU# MU#
dg23 dg23_d0 CL2-A 0 5 h1
#Phantom device group dg13
dg13 dg13_d0 CL2-A 0 5 h2
HORCM _INST
#dev_group ip_address service
dg23 NodeB.dc2.net horcm0 # communicate with DC2 nodes
dg13 NodeA.dc1.net horcm0 # communicate with DC1 nodes
Tri-Link RAID Manager Configuration
The sample RAID Manager configuration files on DC1, DC2, and DC3 nodes for Tri-Link
configuration when using 3DC CAJ/CAJ replication are shown below. The RAID Manager
configuration for Tri-Link configuration when using 3DC Sync/CAJ replication also remains
same except for the MU#s mentioned for the device groups.
NOTE:
• In a 3DC CAJ/CAJ Tri-Link configuration using Delta Resync, only mirror unit descriptors
“1”, “2” and “3” must be used for creating device groups.
• In a 3DC Sync/CAJ configuration, mirror unit descriptor "0" must be used for the device
group between DC1 and DC2.
Sample Raid Manager Configuration on a DC1 NodeA (Tri-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_LDEV
# dev_group dev_name Serial# CU:LDEV(LDEV#) MU#
dg12 dg12_d0 60095 01:04 h1
dg13 dg13_d0 60095 01:04 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 (Tri-Link)
HORCM _MON
#ip_address service poll(10ms) timeout(10ms)
NodeB horcm0 1000 3000
HORCM_CMD
#dev_name dev_name dev_name
114 Designing a Three Data Center Disaster Recovery Solution