High Availability Overview | Teradata Data Mover - High Availability Overview - Teradata Data Mover

Teradata® Data Mover Installation, Configuration, and Upgrade Guide for Customers - 20.01

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Data Mover
Release Number
20.01
Published
November 2023
Language
English (United States)
Last Update
2023-12-05
dita:mapPath
jvt1700556161677.ditamap
dita:ditavalPath
stp1591127384938.ditaval
dita:id
pqq1467243714524
Product Category
Analytical Ecosystem

A high availability configuration is the base configuration for a Data Mover system. If a primary (designated-active) component of a system becomes unavailable, a high availability configuration makes sure that the system continues to function with components running on the secondary (designated-standby) system.

A high availability configuration depends on a monitoring service, which monitors the actively running components and services through SSH connections. If any of the primary services stop running, the failover monitor first attempts to rescue the service. If rescue attempts fail,a failover sequence begins the process of allowing the secondary component to take over for the primary component.

The following monitoring service requirements apply in a high availability environment:
  • The daemon, agent, Data Mover REST, ActiveMQ, and sync monitor service on the primary and secondary components are run using user dmuser
  • The monitoring service cannot be used to monitor Data Mover components if a user other than dmuser has been set up to run these services.
  • The bundled DSA service must be run with the user dscuser.