e.Set the DR_GROUP_NAME variable to the name of DR Group used by this package. This DR Group name is defined when the DR Group is created.
f.Set the DC1_STORAGE_WORLD_WIDE_NAME variable to the world wide name of the EVA storage system which resides in Data Center 1. This WWN can be found on the front panel of the EVA controller, or from command view EVA UI.
g.Set the DC1_SMIS_LIST variable to the list of Management Servers which resides in Data Center 1. Multiple names are defined using a comma as a separator between the names.
If a connection to the first management server fails, attempts are made to connect to the subsequent management servers in the order that they are specified.
h.Set the DC1_HOST_LISTvariable to the list of clustered nodes which resides in Data Center 1. Multiple names are defined using a comma as a separator between the names.
i.Set the DC2_STORAGE_WORLD_WIDE_NAME variable to the world wide name of the EVA storage system which resides in Data Center 2. This WWN can be found on the front panel of the EVA controller, or from command view EVA UI.
j.Set the DC2_SMIS_LIST variable to the list of Management Server, which resides in Data Center 2. Multiple names are defined using a comma as a separator between the names.
If a connection to the first management server fails, attempts are made to connect to the subsequent management servers in the order that they are specified.
k.Set the DC2_HOST _LIST variable to the list of clustered nodes which resides in Data Center 2. Multiple names are defined using a comma as a separator between the names.
l.Set the QUERY_TIME_OUT variable to the number of seconds to wait for a response from the
7.Distribute Metrocluster Continuous Access EVA configuration, environment and control script files to other nodes in the cluster by using ftp, rcp or scp:
# rcp
See the example script Samples/ftpit to see how to
Using ftp may be preferable at your organization, since it does not require the use of a.rhosts file for root. Root access via .rhosts may create a security issue.
8.Apply the Serviceguard configuration using the cmapplyconf command or SAM.
9.Verify that each node in the Serviceguard cluster has the following files in the directory
/etc/cmcluster/pkgname:
bkpbkgname.cntl | Serviceguard package control script |
bkpkgname_caeva.env | Metrocluster Continuous Access EVA environment file |
bkpkgname.ascii | Serviceguard package ASCII configuration file |
bkpkgname.sh | Package monitor shell script, if applicable |
other files | Any other scripts you use to manage Serviceguard packages |
10.Make sure the packages on the source disk site are not running. Using standard Serviceguard commands (cmruncl, cmhaltcl, cmrunpkg, cmhaltpkg) test the target disk site for cluster and package startup and package failover.
11.Any running package on the target disk site that has a counterpart on the source disk site should be halted at this time.
250 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA