Separate HA from a Cluster| Teradata Data Mover - 17.00 - Remove High Availability from a Cluster - Teradata Data Mover

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

Product
Teradata Data Mover
Release Number
17.00
Published
November 30, 2021
Last Update
2021-11-04
Content Type
Administration
Configuration
Installation
Publication ID
B035-4102-030K
Language
English (United States)
Last Update
2021-11-04
Use the following instructions to remove a high availability environment from a cluster. Mention of nn.nn in any filepath refers to the major and minor version numbers of Data Mover.
  1. From the /opt/teradata/client/nn.nn/datamover/failover/ directory on the active daemon, run the following command:
    ./dmcluster configactivemq -e false
  2. From the /opt/teradata/client/nn.nn/datamover/failover/ directory on the standby daemon, run the following command:
    ./dmcluster configactivemq -e false
  3. On the active daemon, find the active monitor server by running the following command:
    ./dmcluster status
  4. From the /opt/teradata/client/nn.nn/datamover/failover/ directory on the active monitor server, run the following command:
    ./dmcluster stopmonitor
  5. Edit the daemon.properties, tdmrest.properties, and agent.properties files on both the active and standby daemons found in the /etc/opt/teradata/datamover directory with the following values:
    • cluster.enabled = false
    • broker.url = localhost
  6. Edit the commandline.properties file with the following values:
    dm.rest.endpoint=https://localhost:1443/datamover
  7. Edit the sync.properties file in both the active and standby daemon in the /etc/opt/teradata/datamover directory with the master.host = localhost value.
  8. Edit the following properties in the failover.properties file on the active daemon as localhost in the /etc/opt/teradata/datamover directory:
    • local.daemon.host
    • remote.daemon.host
    • local.monitor.host
    • local.repository.host
    • remote.repository.host
    • local.agents.host
    • remote.agents.host
  9. From the /opt/teradata/client/nn.nn/datamover/failover directory on the active daemon, run the following command to enter configuration values:
    ./dmcluster config
  10. Restart the tdactivemq, daemon, and agent services for both the active and standby daemon.
    /etc/init.d/tdactivemq stop
    /etc/init.d/tdactivemq start
    /etc/init.d/dmdaemon stop
    /etc/init.d/dmdaemon start
    /etc/init.d/dmagent stop
    /etc/init.d/dmagent start
    /etc/init.d/tdmrest stop
    /etc/init.d/tdmrest start
  11. Run the following command for both the active and standby daemon to verify the daemon is connected to activemq and running on localhost:
    sdt05312:/etc/opt/teradata/datamover # datamove list_jobs
    sdt05312:/etc/opt/teradata/datamover # datamove list_jobs
        Data Mover Command Line 16.20.xx.xx
        2017-12-18 10:26:40 - List Jobs mode 
        Command parameters:
        About to connect to ActiveMQ at localhost:61616
        Connected to Daemon version 16.20.xx.xx
        List jobs...
        Job Name                                                               
    Start          End           Status           Priority
    -------------------------------------------------------------
     No Detailed Information