NOTE: Serviceguard should already be installed on all the cluster nodes. Run swinstall(1m) to install Continentalclusters from an SD depot.

2.When swinstall(1m) has completed, create a directory as follows for the new package in the target disk site.

# mkdir /etc/cmcluster/<package_name>

Create an Serviceguard package configuration file in the target disk site.

#cd /etc/cmcluster/<package_name>

#cmmakepkg -p <package_name>.ascii

Customize it as appropriate to your application. Be sure to include the pathname of the control script (/etc/cmcluster/<package_name>/ <package_name>.cntl) for the RUN_SCRIPT and HALT_SCRIPT parameters. Set the AUTO_RUN flag to NO. This is to ensure the package will not start when the cluster starts. Do not use cmmodpkg to enable package switching on any recovery package. Enabling package switching will automatically start the recovery package. Package switching on a recovery package will be automatically set by the cmrecovercl command on the target disk site when it successfully starts the recovery package.

3.Create a package control script.

# cmmakepkg -s pkgname.cntl

Customize the control script as appropriate to your application using the guidelines in Managing Serviceguard. Standard Serviceguard package customizations include modifying the VG, LV, FS, IP, SUBNET, SERVICE_NAME, SERVICE_CMD and SERVICE_RESTART parameters. Be sure to set LV_UMOUNT_COUNT to 1 or greater.

NOTE: Some of the control script variables, such as VG and LV, on the target disk site must be the same as on the source disk site. Some of the control script variables, such as, FS, SERVICE_NAME, SERVICE_CMD and SERVICE_RESTART are probably the same as on the source disk site. Some of the control script variables, such as IP and SUBNET, on the target disk site are probably different from those on the source disk site. Make sure that you review all the variables accordingly.

4.Add customer-defined run and halt commands in the appropriate places according to the needs of the application. See Managing Serviceguard for more information on these functions.

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/caeva.env \ /etc/cmcluster/pkgname/pkgname_caeva.env

6.Edit the environment file <pkgname>_caeva.env as follows:

a.Set the CLUSTER_TYPE variable to continental

b.Set the PKGDIR variable 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. The operator may create the FORCEFLAG file in this directory. See Appendix B for an explanation of these variables.

c.Set the DT_APPLICATION_STARTUP_POLICY variable to one of two policies:

Availability_Preferred, or Data_Currency_Preferred.

d.Set the WAIT_TIME variable to the timeout, in minutes, to wait for completion of the data merge from source to destination volume before starting up the package on the destination volume. If the wait time expires and merging is still in progress, the package will fail to start with an error that prevents restarting on any node in the cluster.

Completing and Running Continentalclusters Solution with Continuous Access EVA 249