Example: Configuring the Cluster and Starting the Monitoring Service - Teradata Data Mover

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

Product
Teradata Data Mover
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
wcu1482331938115.ditamap
dita:ditavalPath
4102_ICUCustomer_dm_1610.ditaval
dita:id
B035-4102
Product Category
Analytical Ecosystem

The dmcluster config command sets up SSH connections between the DM1, DM2, DM3, VP1, and VP2 servers. These connections are used by the Data Mover monitoring service to monitor the master Data Mover components and initiate a failover if any of the master components stop working.

  1. Enter the following changes to the failover.properties file on the master (DM1) server:
    • local.daemon.host=DM1
    • remote.daemon.host=DM2
    • local.monitor.host=VP1
    • remote.monitor.host=VP2
    • local.repository.host=DM1
    • remote.repository.host=DM2
    • local.agents.host=DM1, DM2, DM3
    • remote.agents.host=DM1, DM2, DM3
  2. Run./dmcluster config as root and follow the following prompts:
    Prompt Action
    Please enter the Root Password for the server running Master Repository: Provide the root Linux password for DM1.
    Please enter the Root Password for the server running Slave Repository: Provide the root Linux password for DM2.
    Please enter the password for root@DM1(MASTER DAEMON): Provide the root Linux password for DM1.
    Please enter the password for root@DM2(SLAVE DAEMON): Provide the root Linux password for DM2.
    Please enter the password for root@VP1(MASTER MONITOR): Provide the root Linux password for VP1.
    Please enter the password for root@VP2(SLAVE MONITOR): Provide the root Linux password for VP1.
    Please enter the password for root@DM3(Master Agent(s)): Provide the root Linux password for DM3.