Configure Failover with an External DSC | Teradata Data Mover - Configuring Failover for Data Mover Using an External DSC - 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
Refer to the following failover configuration steps when running DSA on an external server.
  1. Configure the secondary Data Mover daemon to use the external DSC by editing /etc/opt/teradata/datamover/daemon.properties with the following information:
    dsa.rest.endpoint=http://external_dsc_host:9090/dsa
    is.dsc.colocate.dm=false
    If the external DSA REST server is configured with HTTPS, replace http with https in the dsa.rest.endpoint codeblock.
  2. Stop the DSC on the secondary host using the /etc/init.d/dsc stop command.
  3. Run dmcluster status and verify that the DSC and DSA REST components do not appear in the list of services on either the primary or secondary Data Mover hosts.
    If the DSC or DSA REST component is marked RUNNING or STOPPED, verify that the is.dsc.colocate.dm property is set in the daemon.properties file as false.
    If Data Mover failover occurs, the Data Mover failover monitor automatically fails over to the secondary Data Mover server. If the external DSA fails, both primary and secondary Data Mover servers need to be reconfigured to use the new DSC. See Configuring Data Mover to Use an External DSC.