Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, Reprinted October 2011 (5900-1881)

site site2
For example:
site san_francisco
site san_jose
4. Copy the Metrocluster environment template file to the Site Controller Package directory.
For example:
cp /opt/cmcluster/toolkit/SGCA/xpca.env\
/etc/cmcluster/cw_sc/cw_sc_xpca.env
The command differs based on the arrays that are configured in your environment. For more
information on copy the Metrocluster environment template file based on the arrays in your
environment, see the respective chapters of this manual.
IMPORTANT: When using Metrocluster with Continuous Access XP A.10.00, Metrocluster
with Continuous Access EVA A.05.00, or Metrocluster with EMC SRDF A.09.00, the
Metrocluster environment file parameters are available as part of the package configuration
file. So, you need not complete steps 4, 5, and 6. Instead, edit these environment file
parameters in the package configuration file, cw_sc.config.
5. Edit the Metrocluster environment file to match your environment.
6. Distribute the environment file to all nodes under the Site Controller Package directory.
7. Apply the empty Site Controller Package configuration file.
cmapplyconf -P /etc/cmcluster/cw_sc/cw_sc.config
When the Site Controller Package configuration is applied, the corresponding Site Safety
Latch is also configured automatically in the cluster.
Use the resls command to view the Site Safety Latch resources.
resls -q -s /dts/mcsc/cw_sc
Following is the output that is displayed:
/dts/mcsc/cw_sc: Resource Instance
The current value of the resource is DOWN (0)
Configuring the Site Safety Latch Dependencies for a Complex Workload
After the Site Controller Package configuration is applied, the corresponding Site Safety Latch is
automatically configured in the cluster. This section describes the procedure to configure the Site
Safety Latch dependencies.
Complete the following procedure to configure the Site Safety Latch dependency for a complex
workload:
1. If you have SG SMS CVM or CFS configured as a legacy package in your environment, add
the EMS resource dependency to all the packages that are the foremost predecessors in the
dependency order among the packages that are configured to be managed by the Site
Controller Package on both sites.
Run the following command from a node on both sites:
cfsdgadm add_ems <cw_dg_name> /dts/mcsc/cw_sc 40 "!= DOWN"
NOTE: Specify the condition as != DOWN with a space before the word Down. Ignoring the
space will result in the cfsdgadm command failing.
If you have SLVM configured in your environment, add the EMS resource details in the packages
that are the foremost predecessors in the dependency order among the workload packages
in both the sites.
Configuring Complex Workloads using Site Aware Disaster Tolerant Architecture 357