Designing a Disaster Tolerant Solution Using the Three Data Center Architecture
Designing a Disaster Tolerant Architecture Using Three Data Center with Continuous Access XP
Chapter 6394
5. 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
NOTE If you do not use a package name as a filename for the package
control script, you must follow the convention of the environment file
name. This is the combination of the file name of the package control
script without the file extension, an underscore and type of the data
replication technology (xpca) used. The extension of the file must be
env.
The following examples describe how the environment file name
should be chosen:
Example 1: If the file name of the control script is pkg.cntl, the
environment file name would be pkg_xpca.env.
Example 2: If the file name of the control script is
control_script.sh, the environment file name would be
control_script_xpca.env.
6. Edit the environment file <pkgname>_xpca.env as follows:
a. If necessary, add the path where the Raid Manager software
binaries have been installed to the PATH environment variable.
If the software is in the usual location, /usr/bin, then
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. Explanation of these
variables have been given in the environment template file.
Data currency can not be guaranteed in DC3. In order to recover
the package on DC3, either the AUTO_NONCURDATA variable
should be set to 1 in the package environment file on the DC3
node or the FORCEFLAG needs to be present in the package
directory on the DC3 node.