In a high availability configuration, the ActiveMQ broker is only enabled on the active Data Mover server. The ActiveMQ broker on the standby server is only activated if a failover occurs.
If upgrading from a Data Mover version earlier than 16.20, you must reconfigure the ActiveMQ settings to use only a single active ActiveMQ broker.
- Confirm the network of brokers has been disabled:/opt/teradata/client/nn.nn/datamover/failover/dmcluster configactivemq -e false
- Set the following values for the daemon.properties file on both the active and standby Data Mover servers:
cluster.enabled=false broker.url=localhost or IP address of local system
The Data Mover 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. - Set the following values for the commandline.properties file in both the active and standby Data Mover server, and any other server where the Data Mover command line is installed:
cluster.enabled=true broker.url=active broker url, standby broker url
Providing both broker URLs in commandline.properties allows the command line to automatically connect to whichever Data Mover server is active. - Set the following values for the agent.properties file on both the active and standby server, and any standalone Data Mover agent servers:
cluster.enabled=true broker.url=active broker url, standby broker url
Providing both broker URLs allows the agent to automatically connect to whichever Data Mover daemon is active.