Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access XP P9000 for Linux B.12.00.00

/dev/sdb 0 F CL1-B 0 493 10058 250 OPEN-V
This output displays the mapping between the device files and the CU:LDEVs. In this output
the value for LDEV specifies the CU:LDEV without the : mark.
NOTE: There must also be alternate links for every device, and these alternate links must be
on different buses inside the XP or P9000 disk array. For Example, these alternate links might
be CL2-E and CL2-F.
Unless the devices have been previously paired either on this or another host, the devices will
show up as SMPL (simplex). Paired devices will show up as PVOL (primary volume) or
SVOL(secondary volume).
XP arrays and P9000 arrays support external attached storage devices to be configured as
either PVOL or SVOL or both of a Continuous Access pair. From a Continuous Access
perspective, there is no difference between a pair created from internal devices and a pair
created using external devices.
See the HP StorageWorks XP or P9000 documentation for information about the configuration
requirements of external storage devices attached to XP or P9000 arrays and supported
external storage devices.
9. Determine the devices used by the application package. Define a device group that contains
all of these devices. It is recommended that you use a name that is easily associated with the
package. For Example, a device group name of “db-payroll” is easily associated with the
database for the payroll application. A device group name of “group1” is more difficult to
relate to an application.
Edit the Raid Manager configuration file (horcm0.conf) to include the devices and device
group used by the application package. Only one device group might be specified for all of
the devices that belong to a single application package. These devices are specified in the
field HORCM_DEV or HORCM_LDEV.
Also complete the HORCM_INST field, by supplying the names of only those hosts that are
attached to the XP or P9000 disk array that is remote from the disk array that is directly
attached to this host.
For Example, if node 1 and node 2 are in the source disk site and nodes 3 and node 4 are
in the recovery site, you must specify only nodes 3 and node 4 in the HORCM_INST field in
a file you are creating on node 1 on the source disk site. Node 1 must have previously been
specified in the HORCM_MON field.
10. Restart the Raid Manager instance so that the new information in the configuration file is read.
# horcmshutdown.sh <instance-#>
# horcmstart.sh <instance-#>
11. Repeat these steps on every host that will run this particular application package. If a host
might run more than one application package, you must incorporate device group and host
information for each of these packages.
NOTE: The Raid Manager configuration file must be different for every host, especially for
the HORC_MON and HORC_INST fields.
12. If not previously done, create the paired volumes:
# paircreate -g <devgroup> -f <fencelevel> -vl -c 15
This command must be issued before creating volume groups or disk groups. For creating a
pair of journal groups, see the section, “Pair creation of Journal Groups” (page 19)
CAUTION: Paired devices must be of compatible sizes and types.
18 Configuring an application in a Metrocluster environment