Refer to the following failover configuration steps when running DSA on the Data Mover server and an external server. To run DSA on the Data Mover server, you must have Data Mover 16.20 or later installed.
- Stop the active monitor:
/opt/teradata/client/nn.nn/datamover/failover/dmcluster stopmonitor
- Start the Teradata ActiveMQ and DSC on the standby host:
/etc/init.d/tdactivemq start /etc/init.d/dsc start
- Edit the /etc/opt/teradata/dsa/clienthandler.properties and append the Data Mover host to broker.list as in the following example:
broker.list=153.64.24.162:61616,153.64.24.164:61616,153.64.24.165:61616
- Restart ClientHandlers:/etc/init.d/clienthandler restart
- Configure BAR NC logical netmasks.
- Restart ClientHandlers:
- If the source or target Teradata system version is 16.00 or later, run dsa_configsys on the standby Data Mover server to register the system and restart DSMAIN.If the database version is earlier than 16.00, you cannot pre-configure the standby DSC. You must run dsa_configsys after failover to the standby DSC to promote the standby DSC as the active DSC. You must also restart DSMain, which you can do through dsa_configsys.
- Stop the DSC and tdactivemq on the standby host using the following commands:
/etc/init.d/dsc stop /etc/init.d/tdactivemq stop
- Start the active monitor.
- Run dmcluster status and verify that the DSC and DSA REST components are marked RUNNING on the active Data Mover server and STOPPED on the standby Data Mover server.If failover occurs, the Data Mover failover monitor automatically fails over to the standby server. To enable use of DSA with Data Mover on versions earlier that Teradata Database 16.00, run dsa_configsys on the new active Data Mover server. If the source or target database version is 16.00 or later, running dsa_configsys is not necessary.