Non-target System Designation | Teradata Data Mover - Designating Non-Target Systems - Teradata Data Mover

Teradata® Data Mover User Guide - 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
hlv1700545853003.ditamap
dita:ditavalPath
mpm1591127278842.ditaval
dita:id
don1467241476387
Product Category
Analytical Ecosystem

You can prevent one or more Vantage systems from being a target system for a Data Mover job. This option ensures data is not copied to an unintended target system when running a job.

The systems may be specified either by their TDPID hostnames or their IP addresses, but must be consistent with your system specification in any Data Mover commands. For example, if you specify systems by using their IP addresses for Data Mover commands, you must specify non-target systems by their IP addresses.

  1. Run the list_configuration command to generate configuration.xml.
  2. Open configuration.xml for editing.
  3. For the key job.never.target.system under the property element, set the value element to true.
    The default value for this key is false.
  4. Add the systemList element under value.
  5. For each non-target system, add a targetSystem element and enter the hostname TDPID or IP address of the system.
  6. Close the entry with the /targetSystem element.
  7. Save configuration.xml and run the save_configuration command to update the daemon with the new list of non-target systems.
In the following example configuration.xml, the Vantage systems with TDPID hostnames PROD2 and PROD3 cannot be used as target systems.
<property>
 <key>job.never.target.system</key>
 <value>true</value>
  <systemList>
   <targetSystem>PROD2</targetSystem>
   <targetSystem>PROD3</targetSystem>
  </systemList>
</property>