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 monitoring service uses SSH connections to the servers it monitors. This command typically takes a few minutes to complete and does the following:
  • Sets up the SSH logons for the monitoring services so that they can log on without a password to the servers where the monitored components are installed.
  • Stops all Data Mover services except ActiveMQ on the remote site.
  • Configures and starts the local daemon, agents, and local sync service in master mode.
  • Starts the remote sync service in slave mode.
  • Starts the monitoring service on local.monitor.host to monitor the local Data Mover components.
  1. Log on to the master daemon server and edit the /etc/opt/teradata/datamover/failover.properties file for your system. For details about the Failover.properties file, see Failover.properties File
  2. Run the following command as root: ./dmcluster config
    In a default installation, the master repository host is the same as the master daemon host and the slave repository host is the same as the slave daemon host.