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_LIST variable 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 _LISTvariable 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
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
pkgname.cntl | Serviceguard package control script |
pkgname_caeva.env | Metrocluster Continuous Access EVA environment file |
pkgname.ascii | Serviceguard package ASCII configuration file |
pkgname.sh | Package monitor shell script, if applicable |
other files | Any other scripts used to manage Serviceguard packages |
The Serviceguard cluster is ready to automatically switch packages to nodes in remote data centers using Metrocluster Continuous Access EVA.
10.Using standard Serviceguard commands (cmruncl, cmhaltcl, cmrunpkg, cmhaltpkg), test the source disk site for cluster and package startup and package failover.
11.Any running package on the source disk site that will have a counterpart on the target disk site must be halted at this time.
Setting up a Recovery Package on the Recovery Cluster
Use the procedures in this section to configure a recovery package on the target disk site. Consult the Serviceguard documentation for more detailed instructions on setting up Serviceguard with packages, and for instructions on how to start, halt, and move packages and their services between nodes in a cluster. Use the following steps for the recovery package set up:
1.Install Continentalclusters on all the cluster nodes in the target disk site (skip this step if the software has been pre installed).
248 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA