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

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 resource on each node.
# resls -q -s /dts/mcsc/cw_sc
The 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.
To configure the Site Safety Latch dependency for a complex workload:
1. If you have SLVM, Veritas CVM or SG SMS CVM, or CFS configured in your environment,
add the EMS resource details in the packages that are the root packages among the workload
packages in both the sites.
resource_name /dts/mcsc/cw_sc
resource_polling_interval 120
resource_up_value != DOWN
resource_start automatic
When using SLVM, or VERITAS CVM, or SG SMS CVM/CFS configured as a modular package,
run cmapplyconf to apply the modified package configuration.
2. Verify the Site Safety Latch resource configuration at both sites.
If you have SLVM or Veritas CVM or SG SMS CVM or CFS configured in your environment,
run the following command to view the EMS resource details:
# cmviewcl -v –p <pkg_name>
Modifying Site Controller to manage complex workload
1. Configure the Site Controller Package with complex-workload packages of both sites.
The following example depicts configuring the Site Controller Package with complex workload
packages using CFS:
site san_francisco
critical_package sfo_cw
managed_package sfo_cw_dg
managed_package sfo_cw_mp
site san_jose
critical_package sjc_cw
managed_package sjc_cw_dg
managed_package sjc_cw_mp
NOTE:
• Do not add any comments on the same line after specifying critical or managed packages.
• Always set auto_run parameter to yes for failover packages configured as critical or
managed packages.
• The packages configured with mutual dependency must not be configured as critical or
managed packages.
2. Apply the Site Controller package configuration.
# cmapplyconf -v -P /etc/cmcluster/cw_sc/cw_sc.config
Configuring the Site Controller package for the complex workload 37