NOTE: If not use a package name as a filename for the package control script, it is necessary to 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 (srdf) used. The extension .env of the file must be used. The following examples demonstrate 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_srdf.env.

Example 2: If the file name of the control script is control_script.sh, the environment file name would be control_script_srdf.env.

8.Edit the environment file as follows:

a.Add the path where the EMC Solutions Enabler software binaries have been installed to the PATH environment variable. If the software is installed in the default location,/usr/ symcli/bin, there is no need to set the PATH environment variable in this file.

b.Uncomment the environment variables prefixed with AUTO_. It is recommended to retain the default values of these variables unless there is a specific business requirement to change them. See Appendix B 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 must be unique for each package and is used for status data files. For example, set PKGDIR to/etc/cmcluster/package_name, removing any quotes around the file names.

d.Uncomment the RDF_MODE variables and set it to the RDF mode for RDF pairs in the device group to be Synchronous (sync) or Asynchronous (async).

e.Uncomment the DEVICE_GROUP variables EMC Symmetrix for the local disk array and set it to the Symmetrix device group names given in the symdg list command. If you are using an M by N configuration, configure the DEVICE_GROUP variable with the name of the consistency group.

f.Uncomment the RETRY and RETRYTIME variables. These variables are used to decide how often and how many times to retry the Symmetrix status commands. The defaults should be used for the first package. For other packages RETRYTIME should be altered to avoid contention when more than one package is starting on a node. RETRY * RETRYTIME should be approximately five minutes to keep package startup time under 5 minutes.

 

RETRYTIME

RETRY

 

 

 

pkgA

5 seconds

60 attempts

 

 

 

pkgB

7 seconds

43 attempts

 

 

 

pkgC

9 seconds

33 attempts

 

 

 

g.Uncomment the CLUSTER_TYPE variable and set it to metro. (The value continental is only for use with the Continentalclusters product, described in Chapter 5.)

h.If using an M by N configuration, be sure that the variable CONSISTENCYGROUPS is set to 1 in the environment file

CONSISTENCYGROUPS=1

9.Distribute Metrocluster with EMC SRDF configuration, environment and control script files to other nodes in the cluster by using ftp, rcp or scp:

# rcp -p /etc/cmcluster/pkgname/* \ other_node:/etc/cmcluster/pkgname

274 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC SRDF