Running the Synchronization Service as Master - 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
  1. Run /etc/init.d/dmdaemon stop to stop the daemon service running on the master server.
  2. Ensure the following files are installed on the master server:
    • /etc/opt/teradata/datamover/sync.properties
    • /opt/teradata/datamover/sync/nn.nn/dmsync
    • /opt/teradata/datamover/sync/nn.nn/DMReplication.jar
  3. 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 master service when set to true. If unspecified, the default is false.
    jobstore.host [Optional] Host name of the master server. If unspecified, the default host name of the Data Mover is used.
    jobstore.name [Optional] Logon user ID for the master 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 master 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.
  4. Run /opt/teradata/datamover/sync/nn.nn/dmsync start to start the synchronization service on the master server, where nn.nn is the major and minor version numbers of Data Mover.
    Do not restart the daemon service on the master server until you complete configuration for the slave server and start the slave synchronization service.