Running the Synchronization Service as Slave - Teradata Data Mover

Teradata Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.00
Published
December 2016
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
rdo1467305237457.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem

You can connect one or more slaves simultaneously to a single master repository.

  1. Ensure that the following files are installed on the slave server:
    • /etc/opt/teradata/datamover/sync.properties
    • /opt/teradata/datamover/sync/nn.nn/dmsync
    • /opt/teradata/datamover/sync/nn.nn/DMReplication.jar
  2. Edit values in sync.properties for the following properties:
    Property Description
    master.port Port on which the master synchronization service listens for connections from the slave synchronization service.
    sql.log.directory Where the synchronization service writes log and SQL transaction files.
    sync.isMaster Runs synchronization as a slave service when set to false.
    jobstore.host [Optional] Host name of the slave server. If unspecified, the default host name of the Data Mover is used.
    jobstore.name [Optional] Logon user ID for the slave repository. If unspecified, the default user name of the Data Mover repository is used.
    jobstore.password [Optional] Password for the logon user ID for the slave repository. If unspecified, the default password of the Data Mover repository user is used.
    master.host Name of the host on which the master synchronization service is running.
  3. Run /opt/teradata/datamover/sync/nn.nn/dmsync start to start the synchronization service on the slave server, where nn.nn refers to the major and minor version numbers for Data Mover..
  4. Run /etc/init.d/dmdaemon start to restart the daemon on the master server.