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

1module_version
sg/failovermodule_name
1module_version
dts/dtsmodule_name
1module_version
dts/caevamodule_name
1module_version
failoverpackage_type
*node_name
yesauto_run
nonode_fail_fast_enabled
no_timeoutrun_script_timeout
no_timeouthalt_script_timeout
no_timeoutsuccessor_halt_timeout
/etc/cmcluster/loggscript_log_file
/etc/cmcluster/scripts/dts/mc.shoperation_sequence
/etc/cmcluster/scripts/dts/caeva.shoperation_sequence
$SGCONF/scripts/sg/volume_group.shoperation_sequence
configured_nodefailover_policy
manualfailback_policy
/etc/cmcluster/mccaevadts/dts/dts/dts/dts_pkg_dir
1concurrent_vgchange_operations
0enable_threaded_vgchange
"vgchange -a e"vgchange_cmd
"vxdg -g \${DiskGroup} set cvm_activation_cmd
activation=exclusivewrite"
"vxvol -g \${DiskGroup} startall"vxvol_cmd
datadgvxvm_dg
novxvm_dg_retry
2deactivation_retry_count
nokill_processes_accessing_raw_devices
no_prioritypriority
Replication Modes and Failover Scenarios
While configuring Metrocluster with Continuous Access EVA, the
DT_APPLICATION_STARTUP_POLICY parameter must be configured. This parameter defines
the preferred policy in allowing the application to start in connection with the state of the data in
the local volumes. This parameter can either be set to Availability_Preferred or
Data_Currency_Preferred. In addition, there could be situations when Metrocluster needs
to be forcefully started. In such cases, the FORCEFLAG must be present in the package directory.
Replication Modes and Failover Scenarios 489