A Data Mover job consists of the following:
- A user-provided definition of database objects that Data Mover copies from the source to the target, such as a copy of a table from the PROD1 Teradata Database system to the DEV1 Teradata Database system.
- A programmatically-generated plan of sequential and parallel tasks to optimize job execution, such as distributing job execution into tasks across several servers.
A job is useful for the following tasks:
- Copying database objects.
- Copying one or more tables from an existing Teradata Database system to a backup Teradata Database system, where data in both systems stays synchronized.
- Copying data from a production Teradata Database system to a staging or test Teradata Database system.
- Migrating data regularly in one direction from the original to a backup.
Spaces in the user or account name for the source or target ID cause jobs to fail.The jobs continue to exist after being run, including job definition and history, whether successful or not. You can delete these jobs if they are no longer needed.
Only one instance of a specific job can run at one time.
Data Mover jobs that are created with the command-line or RESTful API move command act the same as running the create command followed by the start command.