|
<< Click to Display Table of Contents >> Navigation: Peer Global File Service Help > File Synchronization Jobs > Running and Managing a File Synchronization Job > Host Connectivity Issues |
Peer Management Center is designed to be run in an environment where all participating hosts are highly available and on highly available networks. The two primary connectivity issues result from:
If a host becomes unavailable while a File Synchronization job is running, and is unreachable within the configured timeout period (specified in the job's General settings), it may be removed from synchronization. If no response is received while performing a file synchronization operation within the timeout period, the Peer Management Center pings the host; if still no response, the host is taken out of the running session, a FATAL event is logged, and the Participants tab for the job is updated to indicate that the host has failed. In addition, if email alerts and/or SNMP notifications are configured and enabled for Host Timeouts, then the appropriate message(s) are sent.
If auto-restart not enabled, you must stop and start the File Synchronization job to bring any failed hosts back into the session. As a result, all root folders on all hosts will need to be scanned again to detect any inconsistencies. Therefore, if you are operating over a WAN with low bandwidth you will want to set the timeout to a higher value on each related job.
For a File Synchronization job to run correctly, a quorum of available hosts must be met. Quorum is currently set to at least 2 hosts, and if quorum is not met, then the synchronization session is automatically be terminated. If email alerts and/or SNMP notifications are configured and enabled for Session Aborts, then the appropriate message(s) are sent.