Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy

1. “ Configuring an empty Site Controller package” (page 36)
2. “Configuring the Site Safety Latch dependencies for a complex workload” (page 37)
3. “Modifying Site Controller to manage complex workload” (page 37)
Configuring an empty Site Controller package
The following are the guidelines that you must follow while configuring an empty Site Controller
package:
• The default value of the priority parameter is set to no_priority. The Site Controller
Package should not be subjected to any movement because of package prioritization. So do
not change this default value.
• The default value of the failover_policy parameter for the Site Controller package is set
to site_preferred. Based on your requirement, the value can be set to
site_preferred_manual.
The site_preferred value implies that during a Site Controller package failover, while
selecting nodes from the list of the node_name entries, the Site Controller Package fails over
to the nodes that belong to the site of the node it last ran on, rather than the nodes that belong
to the other site. The site_preferred_manual failover policy provides automatic failover
of packages within a site and manual failover across sites.
To configure the Site Controller package for the complex workload:
1. From any node, create a Site Controller package configuration file using the dts/sc module.
# cmmakepkg -m dts/sc -m dts/mc3parrc \
/etc/cmcluster/cw_sc/cw_sc.config
2. Edit the cw_sc.config file and specify the following:
IMPORTANT: Ensure there are no packages configured with the critical_package or
managed_package attributes in the Site Controller package configuration file.
a. Name for the package_name attribute.
package_name cw_sc
b. Names of the nodes explicitly using the node_name attribute.
c. The directory created in step 1 for the dts/dts/dts_pkg_dir attribute.
dts/dts/dts_pkg_dir /etc/cmcluster/cw_sc
d. Specify a name for the log file.
script_log_file /etc/cmcluster/cw_sc/cw_sc.log
e. Specify the sites without any packages.
Do not specify any packages using the critical_package or managed_package
attributes.
site site1
site site2
For Example:
site san_francisco
site san_jose
3. Edit 3PAR module parameters in the package configuration file, cw_sc.config to match
your enviromment.
4. Apply the empty Site Controller package configuration file.
# cmapplyconf -P /etc/cmcluster/cw_sc/cw_sc.config
36 Configuring complex workloads using SADTA