Configuration 1: DSC Running on the Data Mover Server
In this configuration, DSC, DSA REST, and Teradata ActiveMQ are running on the designated-active Data Mover server. On the designated-standby server, these components are turned off. If failover occurs, the Data Mover failover monitor automatically turns on the Data Mover components on the designated-standby 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.
|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 active Data Mover server. No pre-configuration can occur in this scenario.|
|16.00 and later||Yes||The DSC on the designated-active and designated-standby servers are registered with the source and target systems during the configuration process, but the DSA ClientHandler cannot be pre-configured to use the designated-standby DSC. If failover occurs, the ClientHandler properties must be updated on all TPA nodes being used and must be restarted.|
Configuration 2: Data Mover using an External DSC
- Backup and restore
- Copying data with Data Mover using the database as a source or target system
Configuration 3: DSC running on the Data Mover server and externally
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.