module_version

1

module_name

sg/failover

module_version

1

module_name

dts/dts

module_version

1

module_name

dts/caeva

module_version

1

package_type

failover

node_name

*

auto_run

yes

node_fail_fast_enabled

no

run_script_timeout

no_timeout

halt_script_timeout

no_timeout

successor_halt_timeout

no_timeout

script_log_file

/etc/cmcluster/logg

operation_sequence

/etc/cmcluster/scripts/dts/mc.sh

operation_sequence

/etc/cmcluster/scripts/dts/caeva.sh

operation_sequence

$SGCONF/scripts/sg/volume_group.sh

failover_policy

configured_node

failback_policy

manual

dts/dts/dts/dts/dts_pkg_dir

/etc/cmcluster/mccaeva

concurrent_vgchange_operations

1

enable_threaded_vgchange

0

vgchange_cmd

"vgchange -a e"

cvm_activation_cmd

"vxdg -g \${DiskGroup} set

activation=exclusivewrite"

 

vxvol_cmd

"vxvol -g \${DiskGroup} startall"

vxvm_dg

datadg

vxvm_dg_retry

no

deactivation_retry_count

2

kill_processes_accessing_raw_devices

no

priority

no_priority

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