Synchronization

The SRP service is designed to run on multiple independent nodes. Within the overall solution architecture, an STP or switch will round-robin or fail-over between the multiple SRP nodes in whichever manner is best suited to the deployment.

As each SRP node is independent, a failure of one node will not directly cause the failure of another node. To achieve independence, no shared connection between the SRP nodes exists.

However, each SRP node must hold and have available the live copy of all audio files and SRP announcement configuration. To achieve the independence of each SRP node, while also providing each node with a copy of the audio data and announcement configuration, the SRP GUI will synchronize its working copy of data across to all SRPs.

This synchronization is achieved using the UNIX tool rsync for efficiency, using SSH as the communication protocol.

File synchronization requires secure passwordless access from the primary SRP where the GUI is enabled through to each active SRP which requires a copy of the data, including itself. To achieve this, an SSH public/private passwordless key is used.