About Configuring High Availability - 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

A High Availability configuration is the base configuration for a Data Mover system. If the primary component of a system goes down, a High Availability configuration ensures that the system continues to function with a secondary component.

This configuration depends on a monitoring service, which monitors the primary, or master, components through SSH connections to see if services are running. If any of the main components are down, a failover sequence begins the process of allowing the slave component to take over for the master component. The daemon, agent, and Sync service that will be monitored by the monitoring service on the master and slave components must be run using user dmuser. The monitoring service cannot be used to monitor the daemon, agent, and Sync service components if a user other than dmuser has been set up to run these services.