Configure Failover with Bundled DSC | Teradata Data Mover - Configuring Failover for DSC Running on the Data Mover Server - 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 the Data Mover server. These steps can be performed prior to a failover event and apply to systems using the following specifications:
  • Data Mover 16.20 or later
  • Teradata system versions are 16.00 or later on both the source and target
  1. Stop the primary monitor:
    /opt/teradata/client/nn.nn/datamover/failover/dmcluster stopmonitor
  2. On the secondary host, start Teradata ActiveMQ and DSC:
    /etc/init.d/tdactivemq start
    /etc/init.d/dsc start
  3. See Configuring the Source and Target Systems section for information on registering the source and target systems with DSC and restart DSMAIN.
  4. Perform the following steps for the source and target TPA nodes with BAR NC ClientHandler software installed:
    1. Append the secondary Data Mover host to broker.list found in the /etc/opt/teradata/dsa/clienthandler.properties file as in the following example:
      broker.list=153.64.24.162:61616,153.64.24.164:61616

      If upgrading, refer to the saved clienthandler.properites file created during the upgrade.

    2. Restart the ClientHandlers.
      /etc/init.d/clienthandler restart
  5. Configure the DSA network, see DSA Network Configuration.
  6. On the secondary host, stop the DSC and tdactivemq:
    /etc/init.d/dsc stop
    /etc/init.d/tdactivemq stop
  7. Start the primary monitor.
  8. Run dmcluster status and verify that the DSC and DSA REST components are marked as RUNNING on the primary Data Mover server and that the DSC and DSA REST components are marked as STOPPED on the secondary Data Mover server.
    If failover occurs, the Data Mover failover monitor automatically fails over to the secondary server. Additional configuration is required to enable Data Mover DSA jobs on the secondary server. Refer to the tasks: