Peer Management Center is designed to be run in an environment where all participating hosts are highly available and on highly available networks.
Unavailable Hosts
If a host becomes unavailable while a File Collaboration job is running, and is unreachable within the configured timeout period (specified within the job's General settings), it may be removed from collaboration. If no response is received while performing a file collaboration operation within the timeout period, then the host will be pinged, and if still no response, the host will be taken out of the running session, a FATAL event will be logged, and the Participants view for the job will be 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) will be sent.
If auto-restart not enabled, you will need to stop and start the File Collaboration job in order 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 jobs.
Quorum
In order for a File Collaboration 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 collaboration session will automatically be terminated. If email alerts and/or SNMP notifications are configured and enabled for Session Aborts, then the appropriate message(s) will be sent.
