according to the needs of the application. See the Managing Serviceguard user’s guide for more information on these variables. Change the Subnet IP from ftp copy.

9.Verify that each host in both clusters in the Continentalclusters has the following files in the directory /etc/cmcluster/<pkg_name>:

<backup_pkg_name>.cntl (Continentalclusters package control script)

<backup_pkg_name>.conf (Serviceguard package ASCII config file)

<backup_pkg_name>.sh (Package monitor shell script, if applicable)

<backup_pkg_name>_srdf.env (Metrocluster SRDF environment file)

10.Split the SRDF logical links for the disks associated with the application package. See the script Samples/pre.cmquery for an example of how to automate this task. The script must be customized with the Symmetrix device group names.

11.Apply the Serviceguard configuration using the cmapplyconf command or SAM for the target disk site.

12.Test the cluster and packages.

#cmruncl

#cmmodpkg -e bkpkgCCA

#cmviewcl -v

Note that cmmodpkg is used to manually start the application packages.

Do all application packages start? If so, then issue the following command.

# cmhaltcl -f

NOTE: Application packages cannot run on R1 and R2 at the same time. Any running package on the source disk site that will have a counterpart on the target disk site must be halted to prevent data corruption.

13.Restore the SRDF logical links for the disks associated with the application package. See the script Samples/post.cmapply for an example of how to automate this task. The script must be customized with the Symmetrix device group names.

The target disk site is now ready for Continentalclusters operation.

Setting up the Continentalclusters Configuration

The procedures below will configure Continentalclusters and the monitoring packages on the two clusters. For complete details on creating and editing the configuration file, refer to Chapter 2: “Designing Continentalclusters”.

1.Split the SRDF logical links for the disks associated with the application package. See the script Samples/pre.cmquery for an example of how to automate this task. The script must be customized with the Symmetrix device group names.

2.Generate the Continentalclusters configuration using the following command:

# cmqueryconcl -C cmconcl.config

3.Edit the configuration file cmconcl.config with the names of the two clusters, the nodes in each cluster, the recovery groups and the monitoring definitions. The recovery groups define the primary and recovery packages. Note that when data replication is done using EMC SRDF, there are no data sender and receiver packages.

Define the monitoring parameters, the notification mechanism (ITO, email, console, SNMP, syslog or tcp) and notification type (alert or alarm) based on the cluster status (unknown, down, up or error). Descriptions for these can be found in the configuration file generated in the previous step.

Building Continentalclusters Solution with EMC SRDF 303