DSA Failover Configurations | Teradata Data Mover - DSA Failover Configurations - Teradata Data Mover

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

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Data Mover
Release Number
20.01
Published
November 2023
Language
English (United States)
Last Update
2023-12-05
dita:mapPath
jvt1700556161677.ditamap
dita:ditavalPath
stp1591127384938.ditaval
dita:id
pqq1467243714524
Product Category
Analytical Ecosystem
How you configure failover with DSA depends on which configuration is used for the DSA environment. For a description of the configurations, see DSA Configurations.
DSA does not support automatic failover. If using the embedded Data Mover DSC, additional configuration may be needed after failover occurs before Data Mover DSA jobs can be run again.

Configuration 1: DSC Running on the Data Mover Server

When there is no external DSA environment, the primary and secondary Data Mover daemons are configured with the bundled DSC provided in the Data Mover package.

Configuration 1: Example Data Mover failover system using the bundled DSA.

In this configuration, DSC, DSA REST, and Teradata ActiveMQ are running on the primary Data Mover server. On the secondary server, these components are turned off. If failover occurs, the Data Mover failover monitor automatically turns on the Data Mover components on the secondary server, including DSC, DSA REST, and Teradata ActiveMQ. However, additional configuration is required before Data Mover DSA jobs can be run on the new active Data Mover server.

Refer to the following considerations based on what version of the Teradata system is running on the source and target systems:
Teradata Version Action Needed Description
Earlier than 16.00 Yes Before running any Data Mover DSA jobs, you must go through all of the steps to configure the DSC on the new secondary Data Mover server. No pre-configuration can occur in this scenario.
16.00 and later No The DSC on the primary and secondary servers are registered with the source and target systems during the configuration process, and the DSA ClientHandler is pre-configured to use the secondary DSC. If failover occurs, no additional action is needed.

Configuration 2: Data Mover using an External DSC

Configuration 2 is used when a Teradata Database with a version earlier than 16.00 has an existing DSA environment and is used for the following:
  • Backup and restore
  • Copying data with Data Mover using the database as a source or target system

Configuration 2: Example Data Mover failover system using an external DSC.
In this configuration, both the primary and secondary servers use the same external DSC. If failover occurs, the failover monitor starts the secondary Data Mover components, which then calls the external DSC. No DSC configuration or registration is necessary if a Data Mover failover occurs.
If the external DSC fails, you need to register a new external DSC with the source and target systems and configure the primary and secondary Data Mover servers to use this new DSC. There is currently no automatic failover for this type of failure.

Configuration 3: DSC running on the Data Mover server and externally

Configuration 3 is when you use both the Data Mover DSC and an external DSC environment on Teradata Databases 16.00 and later.

Configuration 3: Example Data Mover failover system using both the bundled DSC and external DSC.

For failover, this configuration mirrors Configuration 1. The independent, external DSC is not involved in Data Mover failover scenarios. See DSA Failover Configuration 1 for details on the bundled DSC actions.