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
- 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
- Use either the restore_daemon command or, if running Data Mover version 16.20.25.00 or later, the restore template script generated with the backup_daemon command to restore the daemon.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.