Separate HA from a Cluster| Teradata Data Mover - 17.05 - Remove High Availability from a Cluster - 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
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 active daemon in the /opt/teradata/client/nn.nn/datamover/failover/ directory, run the following command:
    ./dmcluster configactivemq -e false
  2. From the standby daemon in the /opt/teradata/client/nn.nn/datamover/failover/ directory, 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 active monitor server in the /opt/teradata/client/nn.nn/datamover/failover/ directory, run the following command:
    ./dmcluster stopmonitor
  5. On both the active and standby daemons in the /etc/opt/teradata/datamover directory, edit the daemon.properties, tdmrest.properties, and agent.properties files 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. From the /opt/teradata/datamover/sync/nn.nn/ directory, run ./dmsync dropconfig to remove the synchronization service from the active to standby repository, see Dropping Existing Synchronization Service.
  8. From the active daemon, edit the following properties in the failover.properties file 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. On both the active and standby daemon, restart the tdactivemq, daemon, REST, and agent services.
    /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
  10. On both the active and standby daemon, run the datamover list_agents command to verify the daemon is connected to ActiveMQ and running on localhost.