Refer to the following failover configuration steps when running DSA on the Data Mover server. These steps can be performed prior to a failover event and apply to systems using the following specifications:
- Data Mover 16.20 or later
- Teradata system versions are 16.00 or later on both the source and target
- Stop the primary monitor:
/opt/teradata/client/nn.nn/datamover/failover/dmcluster stopmonitor
- On the secondary host, start Teradata ActiveMQ and DSC:
/etc/init.d/tdactivemq start /etc/init.d/dsc start
- See Configuring the Source and Target Systems section for information on registering the source and target systems with DSC and restart DSMAIN.
- Perform the following steps for the source and target TPA nodes with BAR NC ClientHandler software installed:
- Append the secondary Data Mover host to broker.list found in the /etc/opt/teradata/dsa/clienthandler.properties file as in the following example:
broker.list=153.64.24.162:61616,153.64.24.164:61616
If upgrading, refer to the saved clienthandler.properites file created during the upgrade.
- Restart the ClientHandlers.
/etc/init.d/clienthandler restart
- Append the secondary Data Mover host to broker.list found in the /etc/opt/teradata/dsa/clienthandler.properties file as in the following example:
- Configure the DSA network, see DSA Network Configuration.
- On the secondary host, stop the DSC and tdactivemq:
/etc/init.d/dsc stop /etc/init.d/tdactivemq stop
- Start the primary monitor.
- Run dmcluster status and verify that the DSC and DSA REST components are marked as RUNNING on the primary Data Mover server and that the DSC and DSA REST components are marked as STOPPED on the secondary Data Mover server.If failover occurs, the Data Mover failover monitor automatically fails over to the secondary server. Additional configuration is required to enable Data Mover DSA jobs on the secondary server. Refer to the tasks: