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

Physical Data Replication for ContinentalClusters Using Continuous Access XP
Setting up a Recovery Package on the Recovery Cluster
Chapter 6 309
6. Copy the environment file template
/opt/cmcluster/toolkit/SGCA/xpca.env to the package directory,
naming it pkgname_xpca.env:
# cp /opt/cmcluster/toolkit/SGCA/xpca.env \
/etc/cmcluster/pkgname/pkgname_xpca.env
7. Edit the environment file <pkgname>_xpca.env as follows:
a. If necessary, add the path where the RaidManager software
binaries have been installed to the PATH environment variable. If
the software is in the usual location, /usr/bin, you can just
uncomment the line in the script.
b. Uncomment the behavioral configuration environment variables
starting with AUTO_. It is recommended that you retain the
default values of these variables unless you have a specific
business requirement to change them. See Appendix A for an
explanation of these variables.
c. Uncomment the PKGDIR variable and set it to the full path name
of the directory where the control script has been placed. This
directory, which is used for status data files, must be unique for
each package. For example, set PKGDIR to
/etc/cmcluster/package_name, removing any quotes around
the file names.
d. Uncomment the DEVICE_GROUP variable and set it to this
package’s Raid Manager device group name, as specified in the
Raid Manager configuration file.
e. Uncomment the HORCMPERM variable and use the default value
MGRNOINST if Raid Manager protection facility is not used or
disabled. If Raid Manager protection facility is enabled set it to
the name of the HORCM permission file.
f. Uncomment the HORCMINST variable and set it to the Raid
Manager instance name used by MetroCluster/CA.
g. Uncomment the FENCE variable and set it to either ASYNC, NEVER,
or DATA according to your business requirements or special
MetroCluster requirements. This variable is used to compare
with the actual fence level returned by the array.
h. If you are using asynchronous data replication, set the
HORCTIMEOUT variable to a value greater than the side file
timeout value configured with the Service Processor (SVP), but