Designing Disaster Tolerant High Availability Clusters, 10th Edition, March 2003 (B7660-90013)

Physical Data Replication for ContinentalClusters Using Continuous Access XP
Preparing the Continental Cluster for Data Replication
Chapter 6292
# horcmstart.sh <instance-#>
12. Repeat these steps on each host that will run this particular
application package. If a host may run more than one application
package, you must incorporate device group and host information for
each of these packages. Note that the Raid Manager configuration
file must be different for each host, especially for the HORC_MON
and HORC_INST fields.
13. If not previously done, you can create the paired volumes by using
the command:
# paircreate -g <devgroup> -f <fencelevel> -vl -c15
This command must be issued before you create volume groups.
WARNING Paired devices must be of compatible sizes and types.
When using the paircreate command to create PVOL/SVOL CA
pairs, specify the -c 15 switch to ensure the fastest data copy from
PVOL to SVOL.
Notes on the Raid Manager Configuration
A single XP device group must be defined for each package on each host
that is connected to the XP series disk array. Device groups are defined
in the Raid Manager configuration file under the heading
"HORCM_DEV".
The disk target IDs and LUNs for all Physical Volumes (PVs) defined in
Volume Groups (VGs) that belong to the package must be defined in one
XP device group on each host system that may ever run one or more
ContinentalClusters packages. The device group name (dev_group) is
user-defined and must be the same on each host in the continental
cluster that accesses the XP disk array. The device group name
(dev_group) must be unique within the cluster; it should be a name that
is easily associated with the application name or MC/ServiceGuard
package name.
The device name (dev_name) is user-defined and must be the same on
each host in the continental cluster that accesses the XP disk array. The
device name (dev_name) must be unique among all devices in the cluster.