Configure Failover with Bundled DSC | Teradata Data Mover - 17.05 - Configuring Failover for DSC Running on the Data Mover Server - Teradata Data Mover

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

prodname
Teradata Data Mover
vrm_release
17.05
created_date
October 2020
category
Administration
Configuration
Installation
featnum
B035-4102-090K
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 designated-active monitor:
    /opt/teradata/client/nn.nn/datamover/failover/dmcluster stopmonitor
  2. On the designated-standby 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 designated-standby 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. Perform the following steps for the source and target TPA nodes with BAR NC ClientHandler software installed:
    1. Remove the designated-standby Data Mover host from broker.list by editing the /etc/opt/teradata/dsa/clienthandler.properties file.
      Leave the designated-active Data Mover host in broker.list.

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

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