Add Source and Target COP Entries | Teradata Data Mover - Adding Source and Target COP Entries - Teradata Data Mover

Teradata® Data Mover Installation, Configuration, and Upgrade Guide for Customers

Product
Teradata Data Mover
Release Number
17.05
Published
October 2020
Language
English (United States)
Last Update
2020-11-18
dita:mapPath
iak1591023586907.ditamap
dita:ditavalPath
stp1591127384938.ditaval
dita:id
B035-4102
lifecycle
previous
Product Category
Analytical Ecosystem

The best way to define the IP addresses for the source and target COP entries is to configure them through DNS. The example below defines the IP addresses for the source and target COP entries in the /etc/hosts file instead because it is easier to explain all of the steps this way.

The IP addresses (COP entries) for all nodes on the source and target systems are placed in the /etc/hosts file so the Data Mover agent can resolve them when running a job. As an example, if the IP addresses of the two nodes on dmdev are 153.64.209.91 and 153.64.209.92, respectively, and the IP addresses of the two nodes on dmtest are 153.64.106.78 and 153.64.106.79, respectively, we add the following entries to the /etc/hosts file on the Data Mover multi-purpose server:
# COP entries for dmdev
153.64.209.91 dmdev dmdevcop1
153.64.209.92 dmdev dmdevcop2

# COP entries for dmtest
153.64.106.78 dmtest dmtestcop1
153.64.106.79 dmtest dmtestcop2

The COP entries for the source and target systems are now in the /etc/hosts file.