Configure DSA after Failover | Teradata Data Mover - Configuring DSA after Failover Occurs

Configure DSA after Failover | Teradata Data Mover - Configuring DSA after Failover Occurs - Teradata Data Mover

Teradata® Data Mover Installation, Configuration, and Upgrade Guide for Customers

Product

Teradata Data Mover

Release Number

17.00

Published

November 30, 2021

Language

English (United States)

Last Update

2021-11-04

dita:mapPath

xmy1574692806525.ditamap

dita:ditavalPath

ffv1503415926374.ditaval

dita:id

B035-4102

lifecycle

Product Category

Analytical Ecosystem

If failover occurs, the Data Mover failover monitor automatically fails over to the standby server. To enable Data Mover DSA jobs on the new active server, follow these steps for source and target TPA nodes with BAR NC ClientHandler software:

Edit the broker.list value in /etc/opt/teradata/dsa/clienthandler.properties
Replace the old active Data Mover host with the new active Data Mover host.
```
broker.list=153.64.24.162:61616
```
Restart ClientHandlers:
/etc/init.d/clienthandler restart

Perform one of the following actions, based on the version of Teradata on your source and target systems:

Teradata Version	Action
16.00 or later	No additional steps are necessary.
Earlier than 16.00	Run dsa_configsys from the new active Data Mover server to register the system Restart DSMAIN. Follow the configuration steps, based on your environment, in the DSA Network Configuration section.