Separate HA from a Cluster| Teradata Data Mover - Remove High Availability from a Cluster - 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
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. From any of the HA configured server in the /opt/teradata/client/nn.nn/datamover/failover/ directory, run the following command:
    ./dmcluster stopmonitor
  4. 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
  5. Edit the commandline.properties file with the following values:
    dm.rest.endpoint=https://localhost:1443/datamover
  6. 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.
  7. From the primary daemon, change the following properties in the /etc/opt/teradata/datamover/failover.properties file to localhost:
    • primary.daemon.host
    • secondary.daemon.host
    • primary.monitor.host
    • primary.repository.host
    • secondary.repository.host
    • primary.agents.host
    • secondary.agents.host
  8. 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
  9. 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.