Deploy Data Mover on VMware | Teradata Data Mover - 17.00 - Deploying Data Mover on VMware - Teradata Data Mover

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

Product
Teradata Data Mover
Release Number
17.00
Published
November 30, 2021
Last Update
2021-11-04
Content Type
Administration
Configuration
Installation
Publication ID
B035-4102-030K
Language
English (United States)
Last Update
2021-11-04
  1. Connect to the vSphere Client through a vCenter server.
  2. On the Home tab, under Inventories, select Hosts and Clusters.
  3. In the Navigator pane, right-click a host and select Deploy OVF Template.
  4. At the Source, Select source step, click Local file, browse to the .ova file from the TVME-DMversion package and click Next.
  5. At the Destination, Select name and folder step, select the name and location for the deployed template and click Next.
  6. At the Setup Networks step, make sure the destination is a public network and click Finish.
    Wait for the deployment to complete.
  7. In the Navigator pane, right-click the VM and select Power > Power On.
  8. Once the VM instance is running, SSH into the instance with the following:
    linux login: root
    Password: iumb123
    The IP address is displayed on the Summary screen of the vSphere client.
    The root logon through the vSphere client is disabled by default.
  9. [Optional] Run -echo "tty1" >> /etc/securetty to enable the root logon through the console.
  10. After login, configure the network:
    1. Gather the following required information to run the network configuration script:
      • VM name (desired hostname for this VM)
      • Public IP address (must be static)
      • Gateway IP address
      • Network domain
      • Primary DNS IP address
      • (Optional) Secondary DNS IP address
      • (Optional) Private IP address – only enter if a separate private network adapter is attached to the VM and you want to configure it.
      • Primary NTP server
      • (Optional) Secondary NTP server
    2. Run the network configuration script:
      # /var/opt/teradata/packages/DataMover/config-network-dm
      After entering the required information, the script configures and restarts the VM instance. Allow several minutes for the configuration to complete after the system is restarted. You can run the script again if necessary if information was entered incorrectly the first time or the configuration changes in the future.
      The following command displays RUNNING for all components when the system is ready:
      # /opt/teradata/datamover/daemon/16.20/dm-control.sh status
      Mon Jan 21 17:31:32 EST 2019  Checking the status of all Teradata DataMover services.
      Checking for Teradata ActiveMQ:          	running
      Checking for Teradata DataMover dmdaemon:	running
      dmdaemon is RUNNING
      Checking for Teradata DataMover dmagent:    	running
      dmagent is RUNNING
      Checking for TMSMonitor:			running
      Checking for Teradata BAR dsc:			running
      dsc is running
       
      Checking for DSARest web service:        	running
      The DSARest web service is running
      Mon Jan 21 17:31:33 EST 2019  Displaying the Teradata database status
      PDE state is RUN/STARTED.
      DBS state is 4: Logons are enabled - Users are logged on
  11. Configure the bundled DSA using the following steps in the order shown:
    1. Install and configure BAR NC on the TPA nodes.
    2. Configure the logical netmask for ClientHandler.
    3. Configure the source and target systems.
  12. Follow the steps in Configuring ActiveMQ on Remote Agents if this is the first time installing or upgrading a standalone agent using this script.
    Once a standalone remote agent has been set up manually, the settings are preserved across upgrades.