Physical data replication with the HP SureStore E Disk Array
XP Series uses the Continuous Access XP integration scripts and
environment file, which are installed in the /usr/sbin and /opt/cmcluster/toolkit/SGCA directories when you install ContinentalClusters. These directories include
the following files:
/opt/cmcluster/toolkit/SGCA/xpca.env—the Continuous Access XP environment file template.
This template must be customized for the specific XP Disk Array and
HP 9000 host system configuration. Copies of this template must
be customized for each separate MC/ServiceGuard package and for
each MC/ServiceGuard Cluster.
/opt/cmcluster/SGCA/Samples-CC—a directory containing sample convenience shell
scripts that must be edited before using. These shell scripts may
help to automate some configuration tasks. These scripts are contributed,
and not supported. This directory also contains example Raid Manager
configuration files and other examples.
/usr/sbin/DRCheckDiskStatus—The script that checks for a specific environment
file in the package directory and should not be edited.
/usr/sbin/DRCheckXPCADevGrp—The script that checks the status of the XP
CA device group that is used by the package and should not be edited.
The Continuous Access XP environment file template should
be used on continental cluster nodes where the following are true:
Data are on an HP SureStore E XP series
disk array.
Data are replicated to a second XP series disk array
using the Continuous Access XP facility.
To use Continuous Access XP data replication in a continental
cluster, the following must also be installed and configured on
each HP 9000 host system that might execute the application:
Raid Manager XP host-based software for control
and status of the XP series disk arrays.
 |
| |
|
 | NOTE: Ensure that you have the most recent version for HP-UX, ContinentalCluster,
Raid Manager, and MC/ServiceGuard by referring to most current ContinentalClusters
release notes. |
|
| |
|
The procedures in this chapter assume that you are configuring
one or more ServiceGuard application packages whose data reside
on the XP disks and are replicated between the two XP disk arrays
with Continuous Access XP. The procedures must be repeated for
each application package.
Continuous Access can be configured in either synchronous or asynchronous
mode. Asynchronous mode is enabled by setting the FENCE parameter to ASYNC in the package configuration ASCII file.
While the cluster is running, all the XP devices (LUNs) that
belong to the same package and are defined in a single Raid Manager
device group must be in the same state at the
same time. Manual changes of these states can cause the package
to halt or to not start up properly due to unexpected conditions.
In general, it is recommended that no manual changes of
state be performed while the package and cluster are running, except
during the repair process. (For example, it is acceptable to run pairresync
to recover from a complete CA link failure. However, if manual changes
are made during the repair process, devices must be returned to
their original states afterwards.)
|
| |
|
 | WARNING! The logic of the special XPCA integration scripts always assumes that
a given PVOL/SVOL state combination was not due
to manual configuration changes. |
|
| |
|
Printable version
