Configuring Automatic Failover - Teradata Data Mover

Teradata Data Mover Installation, Configuration, and Upgrade Guide for Customers

Product
Teradata Data Mover
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
wcu1482331938115.ditamap
dita:ditavalPath
4102_ICUCustomer_dm_1610.ditaval
dita:id
B035-4102
Product Category
Analytical Ecosystem

Data Mover provides automatic failover support when multiple Data Mover servers are configured in a dual environment. Automatic failover configuration must meet the following requirements:

  • Two additional monitoring severs are available to monitor the master and slave components. It is highly recommended that you use a Viewpoint managed server for this purpose.
  • Each monitoring server must be local to the site and ideally be attached to the same network as the components being monitored to avoid automatic failovers caused by network partitions.
  • The DMFailover package must be installed on all servers, including the master and slave daemon, monitoring, and agent servers that are part of the cluster.
If additional monitoring servers are not available, you can enable failover by using the Data Mover synchronization service. The synchronization service alone does not support automatic failover and requires manual intervention to enable failover from master to slave components. If configuring the synchronization service without configuring automatic failover, see Configuring the Synchronization Service Without Automatic Failover.
When using the synchronization service with failover, use the public IP address of the system, not the localhost hostname or the 127.0.0.1 IP address.
The following files, located in the /opt/teradata/client/nn.nn/datamover/failover/ folder, are required when using the monitoring service. Where nn.nn in the filename refers to the major and minor version numbers of Data Mover.
File Description
/etc/opt/teradata/datamover/failover.properties Specifies the master and slave components to be monitored
/opt/teradata/client/nn.nn/datamover/failover/dmcluster Script for setting up SSH log on, configuring the servers in master and slave modes, starting and stopping the monitoring service, and checking the status of the master and slave components
/opt/teradata/client/nn.nn/datamover/failover/DMFailover.jar Executable binary file used for automatic failover
/etc/opt/teradata/datamover/monitor.properties Specifies if Server Management alerts need to be sent if the monitoring service detects a failure. This file is used only on the monitoring server.