In a high availability configuration, the ActiveMQ broker is enabled on the designated-active Data Mover server. The ActiveMQ broker on the designated-standby server is only activated if a failover occurs.
Confirm the network of brokers has been disabled:
/opt/teradata/client/nn.nn/datamover/failover/dmcluster configactivemq -e falseIf upgrading from a Data Mover version earlier than 16.20, you must reconfigure the ActiveMQ settings to use only a single active ActiveMQ broker.
On both the active and standby Data Mover servers, set the following values for the daemon.properties file:
cluster.enabled=false broker.url=localhost or IP address of local systemThe daemon on the active Data Mover server only uses the local ActiveMQ broker. If failover occurs, the daemon on the standby Data Mover sever only uses the ActiveMQ broker on the standby server.
On both the active and standby server, and any standalone Data Mover agent servers, set the following values for the agent.properties file:
cluster.enabled=true broker.url=active broker url,standby broker urlProviding both broker URLs allows the agent to automatically connect to whichever Data Mover daemon is active.
On both the active and standby Data Mover server, and any other server where the Data Mover command line is installed, set the following values for the commandline.properties file:
dm.rest.endpoint=active REST server url,standby REST server urlProviding both REST server URLs in commandline.properties allows the command line to automatically connect to whichever Data Mover server is active.
Make sure the host:port for both the active and standby REST servers are added to the accept.host.list in tdmrest.properties on both the active and standby Data Mover servers.