When a standby server is needed to run a job, it must first be dropped from the synchronization service and then switched to active mode.
Currently Data Mover does not block running jobs if a standby has not been dropped from synchronization service and running jobs on a standby server can cause the following when not dropped from the sync service:
- A replication break between the active and this standby server due to a foreign key or primary key issue. The active server will continue to retry sending the data.
- Jobs may not run successfully.
- Drop the standby server from the synchronization service using the steps in Use Case: Drop One Standby Server from the Synchronization Service.
- Start all Data Mover services on this server such as:
- /etc/init.d/tdactivemq start
- /etc/init.d/dmdaemon start
- /etc/init.d/tdmrest start
- /etc/init.d/dmagent start
- Run jobs on this newly active server.