Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC SRDF
Figure 3 Mapping HP-UX device file names to Symmetrix units
Symmetrix ID 95
SRDF
Node 1
Data Center A Data Center B
Node 2
Node 3
Node 4
R1
R2
GK
BCV
Symmetrix ID 50
R2
R1
GK
1. /dev/rdsk/c0t4d0
2. /dev/rdsk/c0t2d2
3. /dev/rdsk/c0t15d0
4. /dev/rdsk/c4t3d2
5. /dev/rdsk/c6t0d0
6. /dev/rdsk/c0t4d2
7. /dev/rdsk/c0t15d0
8. /dev/rdsk/c4t3d2
9. /dev/rdsk/c4t0d0
10. /dev/rdsk/c3t0d2
11. /dev/rdsk/c3t15d1
12. /dev/rdsk/c0t4d0
13. /dev/rdsk/c4t3d2
14. /dev/rdsk/c5t5d1
1
2
3
4
5
6
7
8
9
12
13
14
10
11
Creating Symmetrix device groups
A single Symmetrix device group must be defined for each package on each node that is connected
to the Symmetrix. You must perform the following procedure on each node that might potentially
run the package:
NOTE: The sample scripts mk3symgrps.nodename can be modified to automate these steps.
1. Use the symdg command, or modify the mk3symgrps.nodename script to define an R1 and
an R2 device group for each package.
# symdg create -type RDF1 devgroupname
Run this command on nodes attached to the R1 side.
# symdg create -type RDF2 devgroupname
Run this command on nodes attached to the R2 side. The devgroupname must be the same
on each node on the R1 and R2 side.
2. Use the symld command to add all LUNs that comprise the Volume Group for that package
on that host to a Symmetrix device group. The HP-UX device file names for all Volume Groups
that belong to the package must be defined in one Symmetrix device group. All devices that
belong to Volume Groups that are owned by an application package must be added to a
single Symmetrix device group.
# symld -g devgroupname add dev devnumber1
# symld -g devgroupname add dev devnumber2
At this point, it is helpful to refer to Table 1 (page 14). Although, the HP-UX device file names
on each node specified may be different, the device group must be the same on each node.
When creating the Symmetrix device groups, specify only one HP-UX path to a particular
Symmetrix device. Do not specify alternate paths (PVLinks). The EMC Solutions Enabler uses
16 Configuring an application in a Metrocluster solution