Site Redundancy

PortaSwitch site redundancy allows to:

  • protect against hosting facility outages
  • provide service to multiple geographic regions when network connectivity between them is lost
  • perform upgrades to new software versions with zero downtime

Why you need it

The only way to overcome catastrophic events and provide uninterrupted service is to have another set of servers in a different location that can continue operating during the outage at the main site.

The per-server redundancy when there are two physical servers and each runs a copy of an application such as PortaSIP, addresses the situation when a single server fails (e.g. hardware fault). However there is another class of catastrophic events that can render all servers installed in the same location (rack, hosting center, etc.) unavailable. Such events include natural disasters, power outages at the collocation provider, network routing errors, etc.

Site Redundancy Diagram

The secondary site (or sites) can be installed in the hosting facility in the same city or in a totally different location across the globe. The only requirement is the sufficient amount of bandwidth between the sites to keep the data replication going.

How it works

Main site unavailable: If the secondary site detects that the main site has become unavailable, the “stand-alone” mode is activated on the secondary site and now it provides the service to end-users using the latest available snapshot of the service configuration.

Secondary site operation: When a service is provided on the secondary site, the billing engine continues to calculate applicable charges according to product, tariff and the responsible party’s other billing parameters (e.g. from the account that originated the call).

Separate DB for changes: All changes to the balance and new xDRs are written into a separate “delta” database running on the same physical server as the stand-by database. This allows the billing engine to keep track of already consumed services and avoid a balance overdraft – even if a secondary site has to operate in stand-alone mode for an extended period of time – and this, therefore, results in a clear history of all produced charges.

Switching back to main site: When the primary site becomes available again, these changes are automatically applied to the primary database – and the secondary site is switched back to “normal” (“stand-by”) mode. All of this happens automatically, without any need for PortaSwitch administrator involvement – and an end-user might not even notice that there were any problems at the main site.

Hardware requirements

A simple redundant site will require 4 servers:

  1. Billing server
  2. DB server
  3. Switching server
  4. Media apps server

The minimal specifications for the servers can be found on the HW requirements page.

contact Of course, this minimal configuration can easily be scaled up, expanded and clustered to increase the maximal load capacity of the secondary site and achieve per-server redundancy at the secondary locations. PortaOne technical sales team will assist you to determine your PortaSwitch network redundancy needs and advise you on the best site redundancy configuration for your project.

NewProcinctus Support Documentation HW Requirements