When configuring the sync service, do not have running jobs on either the active or standby servers and make sure the repositories are in synchronization. You can synchronize the repositories using one of the following methods:
- Before configuration: Run the backup_daemon and restore_daemon commands
- During configuration: Let dmsync config perform the backup and restore during the configuration process
The dmsync config command does not check if there are running jobs when doing a backup and restore of the system. If this is a concern, run the Data Mover backup and restore commands before configuring the synchronization service.
- On the active repository server, go to cd /var/opt/teradata/postgres/data to change the Postgres configuration.
In postgres.conf, change wal_level to logical.
wal_level = logical
Restart the active repository:
- /etc/init.d/postgresql stop
- /etc/init.d/postgresql start
- On the active server , edit the sync.properties file and set the sync.isMaster property to true.
- On the standby server, edit the sync.properties file and set the sync.isMaster property to false.
On the active server, set the dm.pg.jobstore.production.host property in the sync.properties file as the hostname for the active server.
Use a name other than localhost as the host name.
On the active server, configure the sync service:
/opt/teradata/datamover/sync/nn.nn/dmsync configWhere nn.nn in the path refers to the version numbers of Data Mover.
When prompted, respond to the following:
- Select the Setup Replication Service option.
- Provide the standby server name.
- On the standby server, provide the Postgres user credentials.
- Answer y or n to backup and restore the repository from the active to the standby server.
Verify that /var/opt/teradata/logs/dmSync.log is configured properly and the sync monitor is running on the active server.
The monitoring service automatically starts once the configuration process completes successfully.