The Sippy Standby server is essential in three situations:
Stabilizes voice network architectures if the master sever fails
Allows continuity of service While scheduled maintenance takes place
Reduces CPU load on the main server during collection of reports
Options are active failover (hot Standby) and passive failover (warm Standby).
Streaming data replication ensures the mirroring of data to a redundant Sippy Database, delivering data securely to a live standby server.
Sippy employs Slony PostgreSQL for its streaming data replication, resulting in a more flexible and stable mirroring of configurations and call accounting data for your business continuity in the event of failure.
When an issue has been resolved and the primary server becomes available again, any changes to the standby server's copies of databases must be restored back to the primary server. A reversion switchover procedure is performed by Sippy Support, returning original network architecture to normal.