Data Mover provides automatic failover support when multiple Data Mover servers are configured in a master-slave configuration. To use the automatic failover feature, two additional monitoring severs are required to monitor the master and slave components. The monitoring service uses SSH connections to monitor the primary or master components to see if services are running. If any of the main components are down, a failover sequence is initiated. A failover is initiated in the following scenarios:
- The master Data Mover daemon is unavailable
- The master Data Mover repository is unavailable
- All of the master Data Mover agents are unavailable
If the sync service or the tdactivemq is unavailable, a warning message is displayed; however, no failover is initiated in this case.
When a failover occurs, all master components are shut down and the slave components are restarted in master mode. The sync service is restarted in slave mode on the old master. The monitoring service used to monitor the old master components is shut down and the monitoring service is started on the remote site to monitor the new master components.