Failure Scenarios - Teradata Data Mover

Teradata Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
kmo1482331935137.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem

The following is an overview of steps to take after a system or system component has failed and been restored. As with any critical data, save the repository data on a routine basis.

Data Mover Server Goes Down

If the Data Mover server goes down:
  • Use the command backup_daemon to back up the Data Mover repository.
  • To preserve configuration information and logging information, back up the entire Data Mover installation directory on the Data Mover server. The default installation directory for the Data Mover daemon is /opt/teradata/datamover/daemon/ nn.nn. The default installation directory for the Data Mover Agent and Command-Line interface is /opt/teradata/client/nn.nn/datamover.

Recovery after the Data Mover Server is Restored

After the Data Mover server has been restored:
  • Use the command restore_daemon to restore the Data Mover repository.
    The restore_daemon command can only be used if restoring a Data Mover repository that has the same hash algorithm as the Data Mover repository that was backed up by the backup_daemon command.
  • Copy the backed-up Data Mover installation directory to the system, if files were lost.
  • Restart failed jobs that never completed when the Data Mover server failed.

Network Goes Down Between Data Mover Server and Teradata Database Systems

If the network between the Data Mover server and the source and target Teradata Database systems goes down, stop sending jobs to Data Mover. Doing so prevents a backlog in the daemon job queue.

Recovery after the Network is Restored

Restart failed jobs that never completed when the network failed.